Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 935f8a720eeb6bd5c29e01e377d74f0f17a8ce34bdd4188cb9bfb32fe959453b

Tx prefix hash: a1654e4e0c057ef9de9e0d99a76905a07ae4dcf6bcb266ef8850e1c3105be69d
Tx public key: 0ff671bd3e40020e4e3dd9b425953150a371c92089f958e72110a436af1b83cb
Timestamp: 1583932231 Timestamp [UCT]: 2020-03-11 13:10:31 Age [y:d:h:m:s]: 05:212:02:12:05
Block: 80463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1305065 RingCT/type: yes/0
Extra: 010ff671bd3e40020e4e3dd9b425953150a371c92089f958e72110a436af1b83cb02110000002dc48ea382000000000000000000

1 output(s) for total of 332.195288419000 dcy

stealth address amount amount idx
00: d166240aa731a8fb1e9d4b8af471806e416f3358d1c141727806c8cd494079f6 332.195288419000 147259 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": 80473, "vin": [ { "gen": { "height": 80463 } } ], "vout": [ { "amount": 332195288419, "target": { "key": "d166240aa731a8fb1e9d4b8af471806e416f3358d1c141727806c8cd494079f6" } } ], "extra": [ 1, 15, 246, 113, 189, 62, 64, 2, 14, 78, 61, 217, 180, 37, 149, 49, 80, 163, 113, 201, 32, 137, 249, 88, 231, 33, 16, 164, 54, 175, 27, 131, 203, 2, 17, 0, 0, 0, 45, 196, 142, 163, 130, 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