Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2284a6c04d4f459ad5ec275905b67c956d251e1f22cfcc117729020d1340ae06

Tx prefix hash: df58f39dfc3a52787c181253ad592d94892331a1fc75ea711d69795bf3bbf007
Tx public key: b42ec8284329af9aef131f1ad6a9f90c12caa2aa27f3839ae69dbe2af4076fbc
Timestamp: 1574750436 Timestamp [UCT]: 2019-11-26 06:40:36 Age [y:d:h:m:s]: 05:032:02:29:45
Block: 17701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165788 RingCT/type: yes/0
Extra: 01b42ec8284329af9aef131f1ad6a9f90c12caa2aa27f3839ae69dbe2af4076fbc021100000001f95225a5000000000000000000

1 output(s) for total of 536.321179777000 dcy

stealth address amount amount idx
00: b024e76a8fe3b9e646449ca083ee91b0d584f3370c8ffb91c72e84538db24085 536.321179777000 26115 of 0

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": 17711, "vin": [ { "gen": { "height": 17701 } } ], "vout": [ { "amount": 536321179777, "target": { "key": "b024e76a8fe3b9e646449ca083ee91b0d584f3370c8ffb91c72e84538db24085" } } ], "extra": [ 1, 180, 46, 200, 40, 67, 41, 175, 154, 239, 19, 31, 26, 214, 169, 249, 12, 18, 202, 162, 170, 39, 243, 131, 154, 230, 157, 190, 42, 244, 7, 111, 188, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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