Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8af5221929e34516dfbe16352f177a7bdeecd9f7cc081b6ee9f16b2a8cb9a6dd

Tx prefix hash: f7b07ef49116425615f135a5212d573bf54fdbc2c25f9bdc596b2bb29de982f1
Tx public key: c12ced56468e60ae3601a62b6ab5311a3a1f7813d23f88f4cb14e9711502c612
Timestamp: 1681670706 Timestamp [UCT]: 2023-04-16 18:45:06 Age [y:d:h:m:s]: 01:281:05:31:36
Block: 740024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462467 RingCT/type: yes/0
Extra: 01c12ced56468e60ae3601a62b6ab5311a3a1f7813d23f88f4cb14e9711502c612021100000003faf35c9c000000000000000000

1 output(s) for total of 2.167671697000 dcy

stealth address amount amount idx
00: 564bf1e04795109de3272d07f9b02e9a6956accf05ecf2455222601019e21c00 2.167671697000 1186903 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": 740034, "vin": [ { "gen": { "height": 740024 } } ], "vout": [ { "amount": 2167671697, "target": { "key": "564bf1e04795109de3272d07f9b02e9a6956accf05ecf2455222601019e21c00" } } ], "extra": [ 1, 193, 44, 237, 86, 70, 142, 96, 174, 54, 1, 166, 43, 106, 181, 49, 26, 58, 31, 120, 19, 210, 63, 136, 244, 203, 20, 233, 113, 21, 2, 198, 18, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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