Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 705b80909baf81fbe041aeb98870aa729757dddb7cb2cbc0dfe7f88e2c168b24

Tx prefix hash: 330af0d2f95ed6c708a2e25396cf9ce142b7f12cb1123f2610bda08388dc602c
Tx public key: bcd593a246fd1cacb17ed92d97560957f670aeb626d234ccbaa83cebfa16fd45
Timestamp: 1711031792 Timestamp [UCT]: 2024-03-21 14:36:32 Age [y:d:h:m:s]: 01:236:00:21:52
Block: 983228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427360 RingCT/type: yes/0
Extra: 01bcd593a246fd1cacb17ed92d97560957f670aeb626d234ccbaa83cebfa16fd4502110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e8caa81bc9e66db756d4c43644103caf0a8fe7e5e79185823725762001a1ba0 0.600000000000 1443355 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": 983238, "vin": [ { "gen": { "height": 983228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e8caa81bc9e66db756d4c43644103caf0a8fe7e5e79185823725762001a1ba0" } } ], "extra": [ 1, 188, 213, 147, 162, 70, 253, 28, 172, 177, 126, 217, 45, 151, 86, 9, 87, 246, 112, 174, 182, 38, 210, 52, 204, 186, 168, 60, 235, 250, 22, 253, 69, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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