Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d55faa529c11f3da7035efcb09dcbdf94ad3f45387e8be8ba6b0303efac413cd

Tx prefix hash: 9e729b9f8d5b3c0891e079df2ed14682bf6eb9ee2c3408804cb60d950002c06e
Tx public key: 712d0745d9948c9cecb77683f3a10f0b13036bb77d63e9ce7af0b44ba0ecf3f6
Timestamp: 1714140750 Timestamp [UCT]: 2024-04-26 14:12:30 Age [y:d:h:m:s]: 00:347:20:53:30
Block: 1008983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248680 RingCT/type: yes/0
Extra: 01712d0745d9948c9cecb77683f3a10f0b13036bb77d63e9ce7af0b44ba0ecf3f602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a246a47ad8173c4735afeb558f0a9470ec6b8b63b5c1c200c8f22e1f19eac5e 0.600000000000 1470515 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": 1008993, "vin": [ { "gen": { "height": 1008983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a246a47ad8173c4735afeb558f0a9470ec6b8b63b5c1c200c8f22e1f19eac5e" } } ], "extra": [ 1, 113, 45, 7, 69, 217, 148, 140, 156, 236, 183, 118, 131, 243, 161, 15, 11, 19, 3, 107, 183, 125, 99, 233, 206, 122, 240, 180, 75, 160, 236, 243, 246, 2, 17, 0, 0, 0, 1, 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