Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee7125624e96df50c605a9021269f0c3b6afcada4203f5f33d3946798bdf24c2

Tx prefix hash: a42cd391e971efd93971c8a210a834beb5db285404abe7591c06fb864de2ed7d
Tx public key: 1d1e0b885b743642303450d5b037e33d1e0b93c81ab5bf43e7d89ed11678e92c
Timestamp: 1731302944 Timestamp [UCT]: 2024-11-11 05:29:04 Age [y:d:h:m:s]: 00:156:00:04:51
Block: 1151165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111333 RingCT/type: yes/0
Extra: 011d1e0b885b743642303450d5b037e33d1e0b93c81ab5bf43e7d89ed11678e92c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f072020b86de3008e873a760dfe26fb1b19a4e690617c13bb96dd8df0d8d4045 0.600000000000 1636642 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": 1151175, "vin": [ { "gen": { "height": 1151165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f072020b86de3008e873a760dfe26fb1b19a4e690617c13bb96dd8df0d8d4045" } } ], "extra": [ 1, 29, 30, 11, 136, 91, 116, 54, 66, 48, 52, 80, 213, 176, 55, 227, 61, 30, 11, 147, 200, 26, 181, 191, 67, 231, 216, 158, 209, 22, 120, 233, 44, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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