Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce0bd34b8e9c5ac5149d8c13a304232b701c3c65d5fd408758ab9653a11eee33

Tx prefix hash: d2cc93f1453e3ddccf9b541abf738f913b69afcbcfc6a2130ca1fb575d5ba7da
Tx public key: c128ae28adb261826cd9c1f76ebfc46c6cf4c31fe0dba9780f85a0e9473c06b9
Timestamp: 1721013256 Timestamp [UCT]: 2024-07-15 03:14:16 Age [y:d:h:m:s]: 00:313:10:13:26
Block: 1065967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223959 RingCT/type: yes/0
Extra: 01c128ae28adb261826cd9c1f76ebfc46c6cf4c31fe0dba9780f85a0e9473c06b902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aefa815d60ee908434818e01c8d7cab173640ff15cd1e90ab35791d8fb1200a 0.600000000000 1536536 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": 1065977, "vin": [ { "gen": { "height": 1065967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aefa815d60ee908434818e01c8d7cab173640ff15cd1e90ab35791d8fb1200a" } } ], "extra": [ 1, 193, 40, 174, 40, 173, 178, 97, 130, 108, 217, 193, 247, 110, 191, 196, 108, 108, 244, 195, 31, 224, 219, 169, 120, 15, 133, 160, 233, 71, 60, 6, 185, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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