Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ae7a436bc10b39e25003d3163a1f6f4dced51491990a11341abdf898598e1d

Tx prefix hash: d3a7113c3bb497b3de0686d6748bfd543d0e5a1b8a4e364fc535f864bb6ec4be
Tx public key: 782f332ef0b6575e1a75ddd3925d2758823c529b866a290206bfffb23be5c404
Timestamp: 1707810313 Timestamp [UCT]: 2024-02-13 07:45:13 Age [y:d:h:m:s]: 01:325:15:42:10
Block: 956491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491593 RingCT/type: yes/0
Extra: 01782f332ef0b6575e1a75ddd3925d2758823c529b866a290206bfffb23be5c40402110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ab9e3ca9f243209c1f10ebc5037e8c9c68aff9fb9c1bc65dad7b493100e4ce0 0.600000000000 1415799 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": 956501, "vin": [ { "gen": { "height": 956491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ab9e3ca9f243209c1f10ebc5037e8c9c68aff9fb9c1bc65dad7b493100e4ce0" } } ], "extra": [ 1, 120, 47, 51, 46, 240, 182, 87, 94, 26, 117, 221, 211, 146, 93, 39, 88, 130, 60, 82, 155, 134, 106, 41, 2, 6, 191, 255, 178, 59, 229, 196, 4, 2, 17, 0, 0, 0, 10, 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