Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce4dba7f2309ba3894a1a82b8c492bcb027f00ab564fc27ae5342efb2cfa4cc9

Tx prefix hash: aa9678dfbd81fcfa7fbc8c83e7b92e66c82a166644cb721f6f3d05b2b3339b46
Tx public key: ade91db3546ada3af0e1d75aa2cc4afecf6a375ed81a72c986c841ee4ade0c08
Timestamp: 1716366520 Timestamp [UCT]: 2024-05-22 08:28:40 Age [y:d:h:m:s]: 00:246:06:01:17
Block: 1027433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176193 RingCT/type: yes/0
Extra: 01ade91db3546ada3af0e1d75aa2cc4afecf6a375ed81a72c986c841ee4ade0c0802110000000559dad3f5000000000000000000

1 output(s) for total of 0.615580000000 dcy

stealth address amount amount idx
00: 0a9679db61a056d0eecc604c4f65e46b80589bf0e6d4474caf4c51525efd8079 0.615580000000 1495048 of 0

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": 1027443, "vin": [ { "gen": { "height": 1027433 } } ], "vout": [ { "amount": 615580000, "target": { "key": "0a9679db61a056d0eecc604c4f65e46b80589bf0e6d4474caf4c51525efd8079" } } ], "extra": [ 1, 173, 233, 29, 179, 84, 106, 218, 58, 240, 225, 215, 90, 162, 204, 74, 254, 207, 106, 55, 94, 216, 26, 114, 201, 134, 200, 65, 238, 74, 222, 12, 8, 2, 17, 0, 0, 0, 5, 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