Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a24bbada62ba7f520139a80790aa532aa460772df5d5bee07481c2f3d0ddf597

Tx prefix hash: 0409b9eadcf613903d92d9155097522319f388c86b08d23abc65894ed1d27908
Tx public key: 86ce5b7f7d4ff2cae646bfd5c751e128ce065e7bcb00e2e6e7539f5870e2acce
Timestamp: 1708261228 Timestamp [UCT]: 2024-02-18 13:00:28 Age [y:d:h:m:s]: 01:042:05:31:14
Block: 960240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291203 RingCT/type: yes/0
Extra: 0186ce5b7f7d4ff2cae646bfd5c751e128ce065e7bcb00e2e6e7539f5870e2acce0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f47bcc75232b3eaa97a691f285f129783b7af86f4dcad2c7bbb44f5e9a4b7ebc 0.600000000000 1419803 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": 960250, "vin": [ { "gen": { "height": 960240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f47bcc75232b3eaa97a691f285f129783b7af86f4dcad2c7bbb44f5e9a4b7ebc" } } ], "extra": [ 1, 134, 206, 91, 127, 125, 79, 242, 202, 230, 70, 191, 213, 199, 81, 225, 40, 206, 6, 94, 123, 203, 0, 226, 230, 231, 83, 159, 88, 112, 226, 172, 206, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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