Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcbb0d85593dcff87f26ac2fc323ca8c70c14d556f100bfac90c4a061b60af74

Tx prefix hash: 9ffb6d102942b5d997dcc86ac5266e19ddcf30fd8d31e9b89636442d00bad9b8
Tx public key: 6ced65ef94f65b7af9007f3e2b5d12bbe306e8ba1a690ae4ceffc43df7c9bf66
Timestamp: 1755930361 Timestamp [UCT]: 2025-08-23 06:26:01 Age [y:d:h:m:s]: 00:090:03:13:57
Block: 1352515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64345 RingCT/type: yes/0
Extra: 016ced65ef94f65b7af9007f3e2b5d12bbe306e8ba1a690ae4ceffc43df7c9bf660211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57accc92dd9d0f52ad3b8a1edb5103c93222716bbd7359001d57f05d5bfb6c1d 0.600000000000 1840480 of 15

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": 1352525, "vin": [ { "gen": { "height": 1352515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57accc92dd9d0f52ad3b8a1edb5103c93222716bbd7359001d57f05d5bfb6c1d" } } ], "extra": [ 1, 108, 237, 101, 239, 148, 246, 91, 122, 249, 0, 127, 62, 43, 93, 18, 187, 227, 6, 232, 186, 26, 105, 10, 228, 206, 255, 196, 61, 247, 201, 191, 102, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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