Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5364759ff80425a13abfa77d57bfcab0500b42a82375f2b01e22f75ade4bcc1e

Tx prefix hash: b4c970053e6037aa00ba55bfb81b0afe76cd84671c3050b71b6ee9c5ab3d4fc3
Tx public key: bef35c2533fd0fb30145e56aff213af0ff1f74eb39945393dc721f9291719105
Timestamp: 1582434412 Timestamp [UCT]: 2020-02-23 05:06:52 Age [y:d:h:m:s]: 04:277:15:30:53
Block: 70602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091039 RingCT/type: yes/0
Extra: 01bef35c2533fd0fb30145e56aff213af0ff1f74eb39945393dc721f9291719105021100000003724f989b000000000000000000

1 output(s) for total of 358.151742549000 dcy

stealth address amount amount idx
00: d4e580ed9bc54c224af615ed7c57640735081c34d9e4cdc126d88c4700f90570 358.151742549000 130468 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": 70612, "vin": [ { "gen": { "height": 70602 } } ], "vout": [ { "amount": 358151742549, "target": { "key": "d4e580ed9bc54c224af615ed7c57640735081c34d9e4cdc126d88c4700f90570" } } ], "extra": [ 1, 190, 243, 92, 37, 51, 253, 15, 179, 1, 69, 229, 106, 255, 33, 58, 240, 255, 31, 116, 235, 57, 148, 83, 147, 220, 114, 31, 146, 145, 113, 145, 5, 2, 17, 0, 0, 0, 3, 114, 79, 152, 155, 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