Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0b1044d9e3a5fda76425a5fe193d0356296a9686880797ce7fc3a270601991e

Tx prefix hash: ff82ad2c6a4fb06fe76ebe23b8628bfa09ecb51d151aafe37b15ba3f81dbc889
Tx public key: 20f1c6291d1e422c3c6aa1a4a20bd2a30cef1fcbd4daece9277cce1a345b905c
Timestamp: 1729515218 Timestamp [UCT]: 2024-10-21 12:53:38 Age [y:d:h:m:s]: 00:034:00:39:24
Block: 1136405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24310 RingCT/type: yes/0
Extra: 0120f1c6291d1e422c3c6aa1a4a20bd2a30cef1fcbd4daece9277cce1a345b905c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdd5b3cd14ce2240bfce47327af0692e2252e1c34c3964cf22ca7fec08e35f8d 0.600000000000 1619750 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": 1136415, "vin": [ { "gen": { "height": 1136405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdd5b3cd14ce2240bfce47327af0692e2252e1c34c3964cf22ca7fec08e35f8d" } } ], "extra": [ 1, 32, 241, 198, 41, 29, 30, 66, 44, 60, 106, 161, 164, 162, 11, 210, 163, 12, 239, 31, 203, 212, 218, 236, 233, 39, 124, 206, 26, 52, 91, 144, 92, 2, 17, 0, 0, 0, 2, 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