Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a93ab56d0afd130f8720e74b3b279754c679de3e17e0b616a0b8937dd06f23d

Tx prefix hash: 3afb37059e9de358599f60b32ccc47d669a65c67b5bbcb13c43ffae67d4d4d9b
Tx public key: 85307affaff8ee1d70c3efebeb90541f1e4a36b781b1ee5b08b28d5930c93588
Timestamp: 1726002243 Timestamp [UCT]: 2024-09-10 21:04:03 Age [y:d:h:m:s]: 00:195:02:59:40
Block: 1107329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139262 RingCT/type: yes/0
Extra: 0185307affaff8ee1d70c3efebeb90541f1e4a36b781b1ee5b08b28d5930c9358802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb9d06c28bb7db4f212ac4d166a0b38eaabd00edfdcca565b468e79746d4031a 0.600000000000 1584940 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": 1107339, "vin": [ { "gen": { "height": 1107329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb9d06c28bb7db4f212ac4d166a0b38eaabd00edfdcca565b468e79746d4031a" } } ], "extra": [ 1, 133, 48, 122, 255, 175, 248, 238, 29, 112, 195, 239, 235, 235, 144, 84, 31, 30, 74, 54, 183, 129, 177, 238, 91, 8, 178, 141, 89, 48, 201, 53, 136, 2, 17, 0, 0, 0, 3, 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