Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c1866dc4a957222fd61f62a0c72ffc1b9c0887ec04ba42a6b29c9b64ef10412

Tx prefix hash: 8da6a4d537420b4f4a3f8ba80d8b863d2c4f4baac9e139e8d42937d7f39acc0a
Tx public key: e082b912aa8dfc706f0b6ab815e5e75e62aacfb91dc87a8a224aabf390d66e91
Timestamp: 1708893177 Timestamp [UCT]: 2024-02-25 20:32:57 Age [y:d:h:m:s]: 01:254:08:10:43
Block: 965475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440490 RingCT/type: yes/0
Extra: 01e082b912aa8dfc706f0b6ab815e5e75e62aacfb91dc87a8a224aabf390d66e910211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 751e310f6327bf195f66ca6db47dc5ee35f5e16b01130e0ac5d80f392d6cdbec 0.600000000000 1425226 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": 965485, "vin": [ { "gen": { "height": 965475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "751e310f6327bf195f66ca6db47dc5ee35f5e16b01130e0ac5d80f392d6cdbec" } } ], "extra": [ 1, 224, 130, 185, 18, 170, 141, 252, 112, 111, 11, 106, 184, 21, 229, 231, 94, 98, 170, 207, 185, 29, 200, 122, 138, 34, 74, 171, 243, 144, 214, 110, 145, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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