Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbdc7a0adb1e582a1b0469cd9a5b200e297a241b8d829b850154a0dba6425b06

Tx prefix hash: 78682762a559fe0340177a1208e5d235b2e203387ac7d40a4b5c4292e9f76ff4
Tx public key: b766b18261b72dd4ecf2d63a1413a0bf9cf6720dab38e3a241dac31d64254291
Timestamp: 1732052639 Timestamp [UCT]: 2024-11-19 21:43:59 Age [y:d:h:m:s]: 00:007:22:21:00
Block: 1157389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5668 RingCT/type: yes/0
Extra: 01b766b18261b72dd4ecf2d63a1413a0bf9cf6720dab38e3a241dac31d642542910211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc5b4e4678c1a5a075b2a40afc8d3c1f9c8d9985e67aadf31c8cd92608f208be 0.600000000000 1643012 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": 1157399, "vin": [ { "gen": { "height": 1157389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc5b4e4678c1a5a075b2a40afc8d3c1f9c8d9985e67aadf31c8cd92608f208be" } } ], "extra": [ 1, 183, 102, 177, 130, 97, 183, 45, 212, 236, 242, 214, 58, 20, 19, 160, 191, 156, 246, 114, 13, 171, 56, 227, 162, 65, 218, 195, 29, 100, 37, 66, 145, 2, 17, 0, 0, 0, 1, 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