Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 570b2029d8f34c763bbb7851ad335298f638c681f0d63c2271b6001c5dc88805

Tx prefix hash: aae638f00f5378a2d08708577f914264a97f8d6c474e7ff642cb4838e628f036
Tx public key: 31cd3efecbe97d7e6df64aac482022505bbf0cf9c5fbd431c82e570da45e2dcf
Timestamp: 1745160241 Timestamp [UCT]: 2025-04-20 14:44:01 Age [y:d:h:m:s]: 00:048:04:49:55
Block: 1265624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34499 RingCT/type: yes/0
Extra: 0131cd3efecbe97d7e6df64aac482022505bbf0cf9c5fbd431c82e570da45e2dcf0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 960198848d3432951fa35224a675e7025b3da11df16542b10c10ee9ddb5ddd93 0.600000000000 1752837 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": 1265634, "vin": [ { "gen": { "height": 1265624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "960198848d3432951fa35224a675e7025b3da11df16542b10c10ee9ddb5ddd93" } } ], "extra": [ 1, 49, 205, 62, 254, 203, 233, 125, 126, 109, 246, 74, 172, 72, 32, 34, 80, 91, 191, 12, 249, 197, 251, 212, 49, 200, 46, 87, 13, 164, 94, 45, 207, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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