Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0febf44aa6d2b25dc72b0a2a6858d0ccb6f8228a4345e38ea71511b1757fcdba

Tx prefix hash: a637850a58c2b7376d2c3020192520185ba099232356331bef7f09f98c94c37c
Tx public key: 6a9eef33e8573e0a06653372403d9d768ced1b50d586e3105bde81f39ed0e00f
Timestamp: 1736444868 Timestamp [UCT]: 2025-01-09 17:47:48 Age [y:d:h:m:s]: 00:080:19:36:21
Block: 1193756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57533 RingCT/type: yes/0
Extra: 016a9eef33e8573e0a06653372403d9d768ced1b50d586e3105bde81f39ed0e00f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0768f9f1161a5c12b22468c50bd853b38cf812f474cc938fee5a4d7fdf05870 0.600000000000 1680321 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": 1193766, "vin": [ { "gen": { "height": 1193756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0768f9f1161a5c12b22468c50bd853b38cf812f474cc938fee5a4d7fdf05870" } } ], "extra": [ 1, 106, 158, 239, 51, 232, 87, 62, 10, 6, 101, 51, 114, 64, 61, 157, 118, 140, 237, 27, 80, 213, 134, 227, 16, 91, 222, 129, 243, 158, 208, 224, 15, 2, 17, 0, 0, 0, 3, 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