Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5f27c98dbde72f62670c4aab9b92c88dca3642e6f149c0d137e797d7732d16f8

Tx prefix hash: fd6cd21ce806efcdb6395a8c70cdf4f2d89c7497eaee38c2a409ec5e925f395e
Tx public key: ee524c2f6afa24151551a9f5798c8ebfa7e712fae2b6ba29a2c0a234f2756847
Timestamp: 1673001706 Timestamp [UCT]: 2023-01-06 10:41:46 Age [y:d:h:m:s]: 01:330:22:48:59
Block: 668777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497566 RingCT/type: yes/0
Extra: 01ee524c2f6afa24151551a9f5798c8ebfa7e712fae2b6ba29a2c0a234f2756847021100000008e6d27f9c000000000000000000

1 output(s) for total of 3.733052825000 dcy

stealth address amount amount idx
00: 2c84e3657bcf5d1d488f3dace32437805c71e2e18caea8962a6b578a28308c8c 3.733052825000 1110044 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 668787, "vin": [ { "gen": { "height": 668777 } } ], "vout": [ { "amount": 3733052825, "target": { "key": "2c84e3657bcf5d1d488f3dace32437805c71e2e18caea8962a6b578a28308c8c" } } ], "extra": [ 1, 238, 82, 76, 47, 106, 250, 36, 21, 21, 81, 169, 245, 121, 140, 142, 191, 167, 231, 18, 250, 226, 182, 186, 41, 162, 192, 162, 52, 242, 117, 104, 71, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8