Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7b03338d446e2a07e6c34e43408391778b75f6d2aa4b878fb52e9cbaab5567d

Tx prefix hash: 567e8918150d1612108fc5dcddce574173755b6948b5bb83d453dda29721431a
Tx public key: dee78ccb33a05bfd0b76bddc84eeb188fbcdd87f620790ef31603c9985ce6176
Timestamp: 1651847012 Timestamp [UCT]: 2022-05-06 14:23:32 Age [y:d:h:m:s]: 02:311:10:30:30
Block: 495594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742458 RingCT/type: yes/0
Extra: 01dee78ccb33a05bfd0b76bddc84eeb188fbcdd87f620790ef31603c9985ce617602110000000375e3f0e9000000000000000000

1 output(s) for total of 13.992378971000 dcy

stealth address amount amount idx
00: 3f3eadf2a3f57d2adf1fbf66fe6a9d3676210af824a60ed305d930a29b4f9965 13.992378971000 919449 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": 495604, "vin": [ { "gen": { "height": 495594 } } ], "vout": [ { "amount": 13992378971, "target": { "key": "3f3eadf2a3f57d2adf1fbf66fe6a9d3676210af824a60ed305d930a29b4f9965" } } ], "extra": [ 1, 222, 231, 140, 203, 51, 160, 91, 253, 11, 118, 189, 220, 132, 238, 177, 136, 251, 205, 216, 127, 98, 7, 144, 239, 49, 96, 60, 153, 133, 206, 97, 118, 2, 17, 0, 0, 0, 3, 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