Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2474fe82703d075abb624514db2cfa7f081b543cc1b7559e2f6a2c7ad1428481

Tx prefix hash: 0b435b917c72f491aae739f4297b7f525652f19ddc792e7e680bcff754040aed
Tx public key: 09a12c20536451a7e3200ea8d3f0e80f80d5507e6b9cdcc242086e1e82e670c0
Timestamp: 1702585149 Timestamp [UCT]: 2023-12-14 20:19:09 Age [y:d:h:m:s]: 01:036:20:54:52
Block: 913167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287683 RingCT/type: yes/0
Extra: 0109a12c20536451a7e3200ea8d3f0e80f80d5507e6b9cdcc242086e1e82e670c002110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc57d3bf63250337ff40368bc3e98fbd1bba9734ab9b917359341e7f6c6e6743 0.600000000000 1370413 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": 913177, "vin": [ { "gen": { "height": 913167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc57d3bf63250337ff40368bc3e98fbd1bba9734ab9b917359341e7f6c6e6743" } } ], "extra": [ 1, 9, 161, 44, 32, 83, 100, 81, 167, 227, 32, 14, 168, 211, 240, 232, 15, 128, 213, 80, 126, 107, 156, 220, 194, 66, 8, 110, 30, 130, 230, 112, 192, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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