Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 443ef450b8aed8944304bfa8fab72abf16b298d5f506a21ef63037829a949d22

Tx prefix hash: 8c0ea4200d3f9d3da1ad6ab7689eca2c594350936092c4a9aa5a2cbf2e16df24
Tx public key: dac8bb359d5f10a3284bbb51c503418d7b76ebabfffe09b3e3fe07ccf09fe423
Timestamp: 1704261744 Timestamp [UCT]: 2024-01-03 06:02:24 Age [y:d:h:m:s]: 01:321:14:56:00
Block: 927066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488712 RingCT/type: yes/0
Extra: 01dac8bb359d5f10a3284bbb51c503418d7b76ebabfffe09b3e3fe07ccf09fe4230211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb7c28f82db617e709d889eb5a0bc75f85b1fce53e92b9e93d671920aea0b69d 0.600000000000 1384866 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": 927076, "vin": [ { "gen": { "height": 927066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb7c28f82db617e709d889eb5a0bc75f85b1fce53e92b9e93d671920aea0b69d" } } ], "extra": [ 1, 218, 200, 187, 53, 157, 95, 16, 163, 40, 75, 187, 81, 197, 3, 65, 141, 123, 118, 235, 171, 255, 254, 9, 179, 227, 254, 7, 204, 240, 159, 228, 35, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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