Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad4b4c9543535ad9f5e38085696dd631da14775e8206b0a6c175f7ca9d897e8d

Tx prefix hash: 7b975e83245a839eb86e1675adc89b96323d3854d3b05efeaa11bf82e62acd56
Tx public key: 4c7f59d94ea9e13412667caa8496fe2bdc49d5218bed182d98345b87ed2075c9
Timestamp: 1658962069 Timestamp [UCT]: 2022-07-27 22:47:49 Age [y:d:h:m:s]: 03:096:20:14:00
Block: 553139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 848987 RingCT/type: yes/0
Extra: 014c7f59d94ea9e13412667caa8496fe2bdc49d5218bed182d98345b87ed2075c9021100000001d834ebe0000000000000000000

1 output(s) for total of 9.020300417000 dcy

stealth address amount amount idx
00: 9e85fa893473d08ccb035627df94a1f3efdb2d992eefe7ba3b3b9ba1b6f65551 9.020300417000 984911 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": 553149, "vin": [ { "gen": { "height": 553139 } } ], "vout": [ { "amount": 9020300417, "target": { "key": "9e85fa893473d08ccb035627df94a1f3efdb2d992eefe7ba3b3b9ba1b6f65551" } } ], "extra": [ 1, 76, 127, 89, 217, 78, 169, 225, 52, 18, 102, 124, 170, 132, 150, 254, 43, 220, 73, 213, 33, 139, 237, 24, 45, 152, 52, 91, 135, 237, 32, 117, 201, 2, 17, 0, 0, 0, 1, 216, 52, 235, 224, 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