Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b66a744e53ec552572f899cd97b36db2cbebdc03697950e9d670061c66ce41b

Tx prefix hash: 183ff27d1dfb9fcc215e8e553a7fe76f936f9823447c6996fe7204d9bad03072
Tx public key: dfd95e2038f4d8e2d0921add423eea275a68e640929549c2adb57ade2a7f810a
Timestamp: 1721031917 Timestamp [UCT]: 2024-07-15 08:25:17 Age [y:d:h:m:s]: 00:288:19:28:04
Block: 1066123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206353 RingCT/type: yes/0
Extra: 01dfd95e2038f4d8e2d0921add423eea275a68e640929549c2adb57ade2a7f810a02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7dbbba7cbca12972db7e712b0336dd06368f1e3bdc3edf938c2735c661614d3 0.600000000000 1536696 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": 1066133, "vin": [ { "gen": { "height": 1066123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7dbbba7cbca12972db7e712b0336dd06368f1e3bdc3edf938c2735c661614d3" } } ], "extra": [ 1, 223, 217, 94, 32, 56, 244, 216, 226, 208, 146, 26, 221, 66, 62, 234, 39, 90, 104, 230, 64, 146, 149, 73, 194, 173, 181, 122, 222, 42, 127, 129, 10, 2, 17, 0, 0, 0, 10, 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