Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ffeef85f9f0ab127e263633157eacff7797709d6dcad0602aec28bf0173e83c

Tx prefix hash: ce3bfce17e78ebc89dcb6b83b07a86bfddfd1f3c566aea2038c94d40ff7bdc9e
Tx public key: 068443c8963c1b7d095fe79dacd59cee2e9afeba4d071cae521792136ab69e8e
Timestamp: 1740294883 Timestamp [UCT]: 2025-02-23 07:14:43 Age [y:d:h:m:s]: 00:317:13:28:48
Block: 1225333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224810 RingCT/type: yes/0
Extra: 01068443c8963c1b7d095fe79dacd59cee2e9afeba4d071cae521792136ab69e8e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33022c3773c57a1907f975a6c80592eca3f348d9cd00b1334edf1a8e1b22fd5c 0.600000000000 1712198 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": 1225343, "vin": [ { "gen": { "height": 1225333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33022c3773c57a1907f975a6c80592eca3f348d9cd00b1334edf1a8e1b22fd5c" } } ], "extra": [ 1, 6, 132, 67, 200, 150, 60, 27, 125, 9, 95, 231, 157, 172, 213, 156, 238, 46, 154, 254, 186, 77, 7, 28, 174, 82, 23, 146, 19, 106, 182, 158, 142, 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