Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83ac9ce02b5e5bb34d3f75465d1443f209b6bba946eae80553984efde2692e13

Tx prefix hash: 6fdb88f88367a58ce1a52230173b31fc12972e587bda6aa917cd38171d515303
Tx public key: d354a1c321ad9fb17b3f3378103329fe10b053b06849c3a8212f88e7d7659d18
Timestamp: 1734855703 Timestamp [UCT]: 2024-12-22 08:21:43 Age [y:d:h:m:s]: 01:001:14:36:43
Block: 1180623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259543 RingCT/type: yes/0
Extra: 01d354a1c321ad9fb17b3f3378103329fe10b053b06849c3a8212f88e7d7659d180211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 160ef86a4dc84665d06186be3e0e5a2e0fd8424dac0d2712cef839c62f0ba0c0 0.600000000000 1667036 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": 1180633, "vin": [ { "gen": { "height": 1180623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "160ef86a4dc84665d06186be3e0e5a2e0fd8424dac0d2712cef839c62f0ba0c0" } } ], "extra": [ 1, 211, 84, 161, 195, 33, 173, 159, 177, 123, 63, 51, 120, 16, 51, 41, 254, 16, 176, 83, 176, 104, 73, 195, 168, 33, 47, 136, 231, 215, 101, 157, 24, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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