Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 577a018eaca75b185af455d32af0d7ce3896d3b7bf59c21f741e14f9e12a7478

Tx prefix hash: a43115e7b4d3cfc4811307450118f7aa3af140ed9fd328e1799a11d103c8326f
Tx public key: 17d30e288d7324e539b1ecc8a8debd044dc3284b3c064b367b81339a1c24519a
Timestamp: 1739885528 Timestamp [UCT]: 2025-02-18 13:32:08 Age [y:d:h:m:s]: 00:345:20:15:58
Block: 1221943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244874 RingCT/type: yes/0
Extra: 0117d30e288d7324e539b1ecc8a8debd044dc3284b3c064b367b81339a1c24519a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61868d113bfb165a2c08379fda4f6006da4c1d62c4382e72c1178f325fe1c1d0 0.600000000000 1708790 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": 1221953, "vin": [ { "gen": { "height": 1221943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61868d113bfb165a2c08379fda4f6006da4c1d62c4382e72c1178f325fe1c1d0" } } ], "extra": [ 1, 23, 211, 14, 40, 141, 115, 36, 229, 57, 177, 236, 200, 168, 222, 189, 4, 77, 195, 40, 75, 60, 6, 75, 54, 123, 129, 51, 154, 28, 36, 81, 154, 2, 17, 0, 0, 0, 4, 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