Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2551a0dccbf91a9e77a2e8624aaa539b6d7d9533e16f9ece182c19faec041e45

Tx prefix hash: 18474d210c67689941f1587602aeddb2834401dc84e66ebe77e3531ba4ff8562
Tx public key: 21b9ddc77c9ae916473f41ac0e4ca6c047cdb5c8115b97cd20e52494504f68c6
Timestamp: 1708284206 Timestamp [UCT]: 2024-02-18 19:23:26 Age [y:d:h:m:s]: 01:059:07:20:40
Block: 960430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303413 RingCT/type: yes/0
Extra: 0121b9ddc77c9ae916473f41ac0e4ca6c047cdb5c8115b97cd20e52494504f68c60211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ffcc9fc2fd3dc16214c8010c74072785748c0cbc7a97df158d273e5c93a7ba3 0.600000000000 1419995 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": 960440, "vin": [ { "gen": { "height": 960430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ffcc9fc2fd3dc16214c8010c74072785748c0cbc7a97df158d273e5c93a7ba3" } } ], "extra": [ 1, 33, 185, 221, 199, 124, 154, 233, 22, 71, 63, 65, 172, 14, 76, 166, 192, 71, 205, 181, 200, 17, 91, 151, 205, 32, 229, 36, 148, 80, 79, 104, 198, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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