Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32821819ef8cb4b47733b003d1e2051247fd4f301082825b489417888243f10b

Tx prefix hash: e6f6bff0a933d87112bed03ff3d9fdca2d967dba1a05805a0086040c2a888582
Tx public key: 5b0b87f6e83c5a33d5fd33449b81b539a5ade7a42f8a41216942b6ef30421c84
Timestamp: 1736277587 Timestamp [UCT]: 2025-01-07 19:19:47 Age [y:d:h:m:s]: 00:093:03:48:37
Block: 1192366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66365 RingCT/type: yes/0
Extra: 015b0b87f6e83c5a33d5fd33449b81b539a5ade7a42f8a41216942b6ef30421c8402110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a0388bda0fee123edd984f46eb9f652e0d4d88b4f27bda812a2ea877554c2a1 0.600000000000 1678917 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": 1192376, "vin": [ { "gen": { "height": 1192366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a0388bda0fee123edd984f46eb9f652e0d4d88b4f27bda812a2ea877554c2a1" } } ], "extra": [ 1, 91, 11, 135, 246, 232, 60, 90, 51, 213, 253, 51, 68, 155, 129, 181, 57, 165, 173, 231, 164, 47, 138, 65, 33, 105, 66, 182, 239, 48, 66, 28, 132, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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