Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e95d4465fbe2c3ccc50d0e6cb3f005e1e010858ddd031bd8b3ca88a5945fac7b

Tx prefix hash: de785a456831082ca60c636ec5bbfcf57c5e9bf0794d0c88b728058de6da7e06
Tx public key: 699018b0bf6053befb394fac7606f89a1ecb9761b8b8a21ead2c4551926d113c
Timestamp: 1711537700 Timestamp [UCT]: 2024-03-27 11:08:20 Age [y:d:h:m:s]: 01:234:01:37:26
Block: 987430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425944 RingCT/type: yes/0
Extra: 01699018b0bf6053befb394fac7606f89a1ecb9761b8b8a21ead2c4551926d113c02110000002159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0b1fc26e707cd7e77bf362484a2c306f90c3f28ab07ca08ed14bbc041c42209 0.600000000000 1447679 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": 987440, "vin": [ { "gen": { "height": 987430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0b1fc26e707cd7e77bf362484a2c306f90c3f28ab07ca08ed14bbc041c42209" } } ], "extra": [ 1, 105, 144, 24, 176, 191, 96, 83, 190, 251, 57, 79, 172, 118, 6, 248, 154, 30, 203, 151, 97, 184, 184, 162, 30, 173, 44, 69, 81, 146, 109, 17, 60, 2, 17, 0, 0, 0, 33, 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