Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53d952dec11d66fbde638489fa8c6e9618b7a23ef6d5cd55c81b4ae14306d7d5

Tx prefix hash: db882584527ae19b171ddcb8bdfec0164e981aaf8c75dc72b846be0ff15bdc8e
Tx public key: 6e136c9cb7457907c3bcd5904768017c42c74b2fb1d61df27b671e502b6ec356
Timestamp: 1721637300 Timestamp [UCT]: 2024-07-22 08:35:00 Age [y:d:h:m:s]: 00:255:15:47:21
Block: 1071122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182644 RingCT/type: yes/0
Extra: 016e136c9cb7457907c3bcd5904768017c42c74b2fb1d61df27b671e502b6ec35602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8744004f6f9eaddc72db33343768c40e3cf27123cfcb514198fa41593c1eccd 0.600000000000 1543229 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": 1071132, "vin": [ { "gen": { "height": 1071122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8744004f6f9eaddc72db33343768c40e3cf27123cfcb514198fa41593c1eccd" } } ], "extra": [ 1, 110, 19, 108, 156, 183, 69, 121, 7, 195, 188, 213, 144, 71, 104, 1, 124, 66, 199, 75, 47, 177, 214, 29, 242, 123, 103, 30, 80, 43, 110, 195, 86, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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