Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c09e08a2a555288e83450369893c656d2d13f07adc634fb1e9de2a2f1c23237

Tx prefix hash: 9bbe68c6517eb29e4f1877aa7a49f4e3f6c57200c437c145732ff887cdb5ac2b
Tx public key: a25f77fe7a4f0573827d2af5a87a6614a2fe093b343522b3f8f8518ecaf68fcc
Timestamp: 1761885193 Timestamp [UCT]: 2025-10-31 04:33:13 Age [y:d:h:m:s]: 00:021:18:49:44
Block: 1401698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15575 RingCT/type: yes/0
Extra: 01a25f77fe7a4f0573827d2af5a87a6614a2fe093b343522b3f8f8518ecaf68fcc02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5343942928140b1a344d47769a3f533958dfaabf7c6eae8383d5125c3ebe6549 0.600000000000 1890017 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": 1401708, "vin": [ { "gen": { "height": 1401698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5343942928140b1a344d47769a3f533958dfaabf7c6eae8383d5125c3ebe6549" } } ], "extra": [ 1, 162, 95, 119, 254, 122, 79, 5, 115, 130, 125, 42, 245, 168, 122, 102, 20, 162, 254, 9, 59, 52, 53, 34, 179, 248, 248, 81, 142, 202, 246, 143, 204, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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