Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 896c20567a9fd39e20279e9b621e3c7f217c5cf8789d673ece751bfbd9d30ed6

Tx prefix hash: bb789b595e989e98edb7dfee0474f53807ea6ea3fc98ed51e9d55a795821286c
Tx public key: e16a76c1baf2c4e0d4e63e9f85daca1821b46ebb4b9b137f46a460d05318a3d2
Timestamp: 1574533817 Timestamp [UCT]: 2019-11-23 18:30:17 Age [y:d:h:m:s]: 05:170:04:53:59
Block: 15811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1264384 RingCT/type: yes/0
Extra: 01e16a76c1baf2c4e0d4e63e9f85daca1821b46ebb4b9b137f46a460d05318a3d2021100000005b63f0b49000000000000000000

1 output(s) for total of 544.017006664000 dcy

stealth address amount amount idx
00: 5c4f968bb494e7a72acc5aac5075611dc8b179b971e611c647067f2119303398 544.017006664000 21508 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": 15821, "vin": [ { "gen": { "height": 15811 } } ], "vout": [ { "amount": 544017006664, "target": { "key": "5c4f968bb494e7a72acc5aac5075611dc8b179b971e611c647067f2119303398" } } ], "extra": [ 1, 225, 106, 118, 193, 186, 242, 196, 224, 212, 230, 62, 159, 133, 218, 202, 24, 33, 180, 110, 187, 75, 155, 19, 127, 70, 164, 96, 208, 83, 24, 163, 210, 2, 17, 0, 0, 0, 5, 182, 63, 11, 73, 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