Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87a3aabb4df65c3ef2fb8bafb12ed7be544cc9e9ade94509640d8dc7ce3a6324

Tx prefix hash: 9941024726d48811466a992232b544a908a8da6acd1bdb67f89268cb60cf80f1
Tx public key: e632bb08f89cdbf4d9dff7c7df91a8267d3b76e33235d263c95b9617d4502046
Timestamp: 1703232142 Timestamp [UCT]: 2023-12-22 08:02:22 Age [y:d:h:m:s]: 01:143:10:04:52
Block: 918535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363660 RingCT/type: yes/0
Extra: 01e632bb08f89cdbf4d9dff7c7df91a8267d3b76e33235d263c95b9617d450204602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05c5f01718b992fb1a046e83173bec50636a0b5c19a1d2b14eef04269badc3ff 0.600000000000 1376179 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": 918545, "vin": [ { "gen": { "height": 918535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05c5f01718b992fb1a046e83173bec50636a0b5c19a1d2b14eef04269badc3ff" } } ], "extra": [ 1, 230, 50, 187, 8, 248, 156, 219, 244, 217, 223, 247, 199, 223, 145, 168, 38, 125, 59, 118, 227, 50, 53, 210, 99, 201, 91, 150, 23, 212, 80, 32, 70, 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