Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ea01a102abc335361613ecca0c5d8ceb8ddd3dfe19023a99e49acaef1e59687

Tx prefix hash: 5483398a7ac56c0cbe479a64c02652990a7e820b7851e1344a6b3f7b3ed48625
Tx public key: 6bcf3d322bb1f36803230b41f798a91cfdc26c8a34bb1e4c69a3f10ac3d68c08
Timestamp: 1753620031 Timestamp [UCT]: 2025-07-27 12:40:31 Age [y:d:h:m:s]: 00:069:10:21:49
Block: 1334506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48393 RingCT/type: yes/0
Extra: 016bcf3d322bb1f36803230b41f798a91cfdc26c8a34bb1e4c69a3f10ac3d68c08021100000008ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 848f025517a93b30a4b070f5ea5a274195f2b615b02e652f36592363caa8706d 0.600000000000 1822307 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": 1334516, "vin": [ { "gen": { "height": 1334506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "848f025517a93b30a4b070f5ea5a274195f2b615b02e652f36592363caa8706d" } } ], "extra": [ 1, 107, 207, 61, 50, 43, 177, 243, 104, 3, 35, 11, 65, 247, 152, 169, 28, 253, 194, 108, 138, 52, 187, 30, 76, 105, 163, 241, 10, 195, 214, 140, 8, 2, 17, 0, 0, 0, 8, 239, 34, 20, 133, 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