Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70bbe40638ef3c763832f0be2a10f41504a2f31935006a2a06712f03fdac5730

Tx prefix hash: 474ce75a9f3791fd383db47aa02b9709051c4f383e390952484f50168cb694e3
Tx public key: 9e09f1127e7a1fdfa723c624d1febf0878fb2c7c652c7d960beb6af5239059fc
Timestamp: 1712665179 Timestamp [UCT]: 2024-04-09 12:19:39 Age [y:d:h:m:s]: 01:044:09:14:11
Block: 996721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292736 RingCT/type: yes/0
Extra: 019e09f1127e7a1fdfa723c624d1febf0878fb2c7c652c7d960beb6af5239059fc02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c50aed718bba10f997e7babdf8e6edd13a7a87eeabf753f71d75b84a744152e9 0.600000000000 1457147 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": 996731, "vin": [ { "gen": { "height": 996721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c50aed718bba10f997e7babdf8e6edd13a7a87eeabf753f71d75b84a744152e9" } } ], "extra": [ 1, 158, 9, 241, 18, 126, 122, 31, 223, 167, 35, 198, 36, 209, 254, 191, 8, 120, 251, 44, 124, 101, 44, 125, 150, 11, 235, 106, 245, 35, 144, 89, 252, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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