Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d4b34c008625383f9ad5c649207354a5a8156cbe0ed0361585ebe234d776e2d

Tx prefix hash: b2d5e7add2ce2923784e5dd25863649f592dbd6dfbdcb7839fce94e497913e80
Tx public key: 964abd1ffd29c4d6751bfc9658071bcad1a3a6786276dc175a0f6d302a7b47f1
Timestamp: 1729924634 Timestamp [UCT]: 2024-10-26 06:37:14 Age [y:d:h:m:s]: 00:029:04:30:38
Block: 1139800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20843 RingCT/type: yes/0
Extra: 01964abd1ffd29c4d6751bfc9658071bcad1a3a6786276dc175a0f6d302a7b47f10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c397cc64ffad0e393693a106ee6a825ba7ec6cd206d26e8091eb70b4ecb4c3e0 0.600000000000 1623587 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": 1139810, "vin": [ { "gen": { "height": 1139800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c397cc64ffad0e393693a106ee6a825ba7ec6cd206d26e8091eb70b4ecb4c3e0" } } ], "extra": [ 1, 150, 74, 189, 31, 253, 41, 196, 214, 117, 27, 252, 150, 88, 7, 27, 202, 209, 163, 166, 120, 98, 118, 220, 23, 90, 15, 109, 48, 42, 123, 71, 241, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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