Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a32296be4e8a49beb5155474dd920fd0372fc0f35735479c3f961e2790ecaa9

Tx prefix hash: e9362a0e8e0de3ff52c8ed1bf307fd0cd484296d120c16f4b8db233c5a47d11e
Tx public key: b2cc4795ce5b412e5fa047cde0089985a2e95f8caf0bb367d08ac185414da960
Timestamp: 1697205943 Timestamp [UCT]: 2023-10-13 14:05:43 Age [y:d:h:m:s]: 01:187:17:49:05
Block: 868789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395215 RingCT/type: yes/0
Extra: 01b2cc4795ce5b412e5fa047cde0089985a2e95f8caf0bb367d08ac185414da960021100000001e08532b6000000000000000000

1 output(s) for total of 0.811598846000 dcy

stealth address amount amount idx
00: 1a2b14a95ca7f3ae0d064a03a9ab9fb8471c193e71616c7a3b2ae9add459b19e 0.811598846000 1323608 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": 868799, "vin": [ { "gen": { "height": 868789 } } ], "vout": [ { "amount": 811598846, "target": { "key": "1a2b14a95ca7f3ae0d064a03a9ab9fb8471c193e71616c7a3b2ae9add459b19e" } } ], "extra": [ 1, 178, 204, 71, 149, 206, 91, 65, 46, 95, 160, 71, 205, 224, 8, 153, 133, 162, 233, 95, 140, 175, 11, 179, 103, 208, 138, 193, 133, 65, 77, 169, 96, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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