Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6983a0b2f206aedf38a9eb48c42aee7eee010ebcf46cfad1641621c0662e721d

Tx prefix hash: 2c39a23c78441b81799c6498a7026e75f3a881fdb73b05eb934bc00b1973e797
Tx public key: ee29f09183e91af6a76d718d9042177a552d1be7b5db096136e55275e1dcd9f8
Timestamp: 1731806151 Timestamp [UCT]: 2024-11-17 01:15:51 Age [y:d:h:m:s]: 00:211:08:20:04
Block: 1155330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150816 RingCT/type: yes/0
Extra: 01ee29f09183e91af6a76d718d9042177a552d1be7b5db096136e55275e1dcd9f80211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d80809149e0c82c9e56d3273eb8fff2d18ecf227e5dc056f284de475dc62d8bd 0.600000000000 1640945 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": 1155340, "vin": [ { "gen": { "height": 1155330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d80809149e0c82c9e56d3273eb8fff2d18ecf227e5dc056f284de475dc62d8bd" } } ], "extra": [ 1, 238, 41, 240, 145, 131, 233, 26, 246, 167, 109, 113, 141, 144, 66, 23, 122, 85, 45, 27, 231, 181, 219, 9, 97, 54, 229, 82, 117, 225, 220, 217, 248, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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