Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42f96e7a03988e9ad24407e26fbb3eb97696ec61d1be74095dd9eb771775ce17

Tx prefix hash: d41df54288a3e710d6585e0a3c8ff5f16a6ee16538607903ed936a7a3f7f4742
Tx public key: 6d98127ac76168d2ea433f3c97bc160d18b43e62def7f59c47abb80ef6fbc530
Timestamp: 1699198562 Timestamp [UCT]: 2023-11-05 15:36:02 Age [y:d:h:m:s]: 01:146:20:59:56
Block: 885102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366167 RingCT/type: yes/0
Extra: 016d98127ac76168d2ea433f3c97bc160d18b43e62def7f59c47abb80ef6fbc53002110000000233af99f4000000000000000000

1 output(s) for total of 0.716621207000 dcy

stealth address amount amount idx
00: d047affa5b50630c8ca2b12e4ca96544af065279b08e47ab530a25e1df7f8fa8 0.716621207000 1340855 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": 885112, "vin": [ { "gen": { "height": 885102 } } ], "vout": [ { "amount": 716621207, "target": { "key": "d047affa5b50630c8ca2b12e4ca96544af065279b08e47ab530a25e1df7f8fa8" } } ], "extra": [ 1, 109, 152, 18, 122, 199, 97, 104, 210, 234, 67, 63, 60, 151, 188, 22, 13, 24, 180, 62, 98, 222, 247, 245, 156, 71, 171, 184, 14, 246, 251, 197, 48, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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