Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9e712b6b7ab455653f2cdb3dfad26e40d359506b616be16ab159c66df39fe56

Tx prefix hash: c7ea482aab3c1706f55c87303c9b19799ac1221c0ea554fb37fe8a7cbd7a02f0
Tx public key: c684bc06bce17bdc14be0d3b994ddcccc3e6629c3b23647cecdb1a343f0b5827
Timestamp: 1712481807 Timestamp [UCT]: 2024-04-07 09:23:27 Age [y:d:h:m:s]: 01:051:18:58:37
Block: 995203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298035 RingCT/type: yes/0
Extra: 01c684bc06bce17bdc14be0d3b994ddcccc3e6629c3b23647cecdb1a343f0b582702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4eb5a36ebe073cc44a65537f25270a03374ced7c88e59ad05a24ca502924cd8 0.600000000000 1455609 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": 995213, "vin": [ { "gen": { "height": 995203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4eb5a36ebe073cc44a65537f25270a03374ced7c88e59ad05a24ca502924cd8" } } ], "extra": [ 1, 198, 132, 188, 6, 188, 225, 123, 220, 20, 190, 13, 59, 153, 77, 220, 204, 195, 230, 98, 156, 59, 35, 100, 124, 236, 219, 26, 52, 63, 11, 88, 39, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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