Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20eccd228232a658f37cd108ccfe43ed3df770fdd5a0437b48aa3fe4159240c9

Tx prefix hash: d12c137aee91325e6a15f71d15763f5dcc7cdeb5e567f7bb9a21b2448bf9b821
Tx public key: 486d3f7632f2ee96c9981b4f40dc1282cb83a5da5d0fcc703bcf1bf882fe0171
Timestamp: 1709921795 Timestamp [UCT]: 2024-03-08 18:16:35 Age [y:d:h:m:s]: 01:073:15:47:08
Block: 974016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313663 RingCT/type: yes/0
Extra: 01486d3f7632f2ee96c9981b4f40dc1282cb83a5da5d0fcc703bcf1bf882fe017102110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21959506fd887778a2fe01444ddec23a15b387685fcc0fd37ecf85c53520f1be 0.600000000000 1433959 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": 974026, "vin": [ { "gen": { "height": 974016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21959506fd887778a2fe01444ddec23a15b387685fcc0fd37ecf85c53520f1be" } } ], "extra": [ 1, 72, 109, 63, 118, 50, 242, 238, 150, 201, 152, 27, 79, 64, 220, 18, 130, 203, 131, 165, 218, 93, 15, 204, 112, 59, 207, 27, 248, 130, 254, 1, 113, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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