Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47926a55d0605fa97dba1fc4a27cf238f5654b2769bc66045522eb37dbca635a

Tx prefix hash: 8a127ab29eae71ee3a43a4c6fadac61958d92a00ce6009e0ab5de5bd305a6fd9
Tx public key: 5ab2563bcadb0a938a8c87b44a4b520304615522df869fcf0036b136caaf982e
Timestamp: 1638780262 Timestamp [UCT]: 2021-12-06 08:44:22 Age [y:d:h:m:s]: 02:348:01:49:37
Block: 389550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766787 RingCT/type: yes/0
Extra: 015ab2563bcadb0a938a8c87b44a4b520304615522df869fcf0036b136caaf982e021100000044d6e4826b000000000000000000

1 output(s) for total of 31.423858235000 dcy

stealth address amount amount idx
00: 1f09c9431a065c1a7ecc5e014aa5cd6aff9bd419d9f2f5c592037964ba5c2644 31.423858235000 784757 of 0

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": 389560, "vin": [ { "gen": { "height": 389550 } } ], "vout": [ { "amount": 31423858235, "target": { "key": "1f09c9431a065c1a7ecc5e014aa5cd6aff9bd419d9f2f5c592037964ba5c2644" } } ], "extra": [ 1, 90, 178, 86, 59, 202, 219, 10, 147, 138, 140, 135, 180, 74, 75, 82, 3, 4, 97, 85, 34, 223, 134, 159, 207, 0, 54, 177, 54, 202, 175, 152, 46, 2, 17, 0, 0, 0, 68, 214, 228, 130, 107, 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