Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e5b656f059564f9d0a9aac77a5e58859f53c37f740ad80f7f47b66c2bfb39cb

Tx prefix hash: 66943a29403f85436c56f9a92ae913f65b721dd6f9603a3ce2bf2d32ee0074c2
Tx public key: 247d25b14cd06ae56763f520285d95c83a7966a8507d83f027f6c3c8af220e4e
Timestamp: 1740947986 Timestamp [UCT]: 2025-03-02 20:39:46 Age [y:d:h:m:s]: 00:258:07:54:24
Block: 1230764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182375 RingCT/type: yes/0
Extra: 01247d25b14cd06ae56763f520285d95c83a7966a8507d83f027f6c3c8af220e4e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc4b37c39d5fb3013ec750a02de67bedeed01a162fc23d0cd4e1aaf99400d793 0.600000000000 1717663 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": 1230774, "vin": [ { "gen": { "height": 1230764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc4b37c39d5fb3013ec750a02de67bedeed01a162fc23d0cd4e1aaf99400d793" } } ], "extra": [ 1, 36, 125, 37, 177, 76, 208, 106, 229, 103, 99, 245, 32, 40, 93, 149, 200, 58, 121, 102, 168, 80, 125, 131, 240, 39, 246, 195, 200, 175, 34, 14, 78, 2, 17, 0, 0, 0, 3, 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