Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afb8e1f011fc40931c3e5d334b87c2596f922db5d41f6852096b3f3e6668eb3b

Tx prefix hash: 5581bddb85ee36b357eb4479455df57b8126c88b8b720fa1206274939cf71ecd
Tx public key: b8ac66267dd6e3e7be24ebd6f8288908de233fe7b795e8ba5bd6f8e369daa31c
Timestamp: 1574754382 Timestamp [UCT]: 2019-11-26 07:46:22 Age [y:d:h:m:s]: 05:038:10:10:31
Block: 17737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170294 RingCT/type: yes/0
Extra: 01b8ac66267dd6e3e7be24ebd6f8288908de233fe7b795e8ba5bd6f8e369daa31c021100000001f95225a5000000000000000000

1 output(s) for total of 536.081519806000 dcy

stealth address amount amount idx
00: e946e54c7b6e1c0c7782204fa4ff5bd8a0c42d5fd747dabcf668793ac591cfd8 536.081519806000 26229 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": 17747, "vin": [ { "gen": { "height": 17737 } } ], "vout": [ { "amount": 536081519806, "target": { "key": "e946e54c7b6e1c0c7782204fa4ff5bd8a0c42d5fd747dabcf668793ac591cfd8" } } ], "extra": [ 1, 184, 172, 102, 38, 125, 214, 227, 231, 190, 36, 235, 214, 248, 40, 137, 8, 222, 35, 63, 231, 183, 149, 232, 186, 91, 214, 248, 227, 105, 218, 163, 28, 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