Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4efd0edc30e33bfdd06494809c45c781354ecd40cd0c60a1dfbd304f3b7eac7

Tx prefix hash: f61852334df64b8fecb905b0032570684a1aa3e91e8c3c1e910d17aeb86b69fb
Tx public key: 60a14e618e34627eef3fd3fe7a47212e7880147c44cd27000019ee2a04373b2c
Timestamp: 1706436450 Timestamp [UCT]: 2024-01-28 10:07:30 Age [y:d:h:m:s]: 01:134:13:05:48
Block: 945081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357297 RingCT/type: yes/0
Extra: 0160a14e618e34627eef3fd3fe7a47212e7880147c44cd27000019ee2a04373b2c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df30f33a66dcd86646872aa53d09965da1b614a2a3e95e4ae864ca5ce3babc23 0.600000000000 1403389 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": 945091, "vin": [ { "gen": { "height": 945081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df30f33a66dcd86646872aa53d09965da1b614a2a3e95e4ae864ca5ce3babc23" } } ], "extra": [ 1, 96, 161, 78, 97, 142, 52, 98, 126, 239, 63, 211, 254, 122, 71, 33, 46, 120, 128, 20, 124, 68, 205, 39, 0, 0, 25, 238, 42, 4, 55, 59, 44, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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