Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9f655c20c460654d501579d29b8fb7e56e9c7388cadcca209684a5f2d0e2d09

Tx prefix hash: 940ef22c6d40f021237db0e48541ade7be81aa3c118d3e242bbc3519c42eb8d8
Tx public key: 10f1bd19baa84ef93b320ebd88bd80d4c7dc8a618c33d199e4e613971394a41a
Timestamp: 1762971868 Timestamp [UCT]: 2025-11-12 18:24:28 Age [y:d:h:m:s]: 00:041:10:18:55
Block: 1410687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29663 RingCT/type: yes/0
Extra: 0110f1bd19baa84ef93b320ebd88bd80d4c7dc8a618c33d199e4e613971394a41a02110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deac5166407b92f4b27e1431e4c5b1244627ff5d28271b85235a3cd03532f1e8 0.600000000000 1899140 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": 1410697, "vin": [ { "gen": { "height": 1410687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deac5166407b92f4b27e1431e4c5b1244627ff5d28271b85235a3cd03532f1e8" } } ], "extra": [ 1, 16, 241, 189, 25, 186, 168, 78, 249, 59, 50, 14, 189, 136, 189, 128, 212, 199, 220, 138, 97, 140, 51, 209, 153, 228, 230, 19, 151, 19, 148, 164, 26, 2, 17, 0, 0, 0, 5, 112, 96, 157, 3, 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