Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a29947ca7e529cfb08af572c6f70e0bf71b230a92542f2bfbedbc3b806354ee

Tx prefix hash: 2c376f7f2d67bc60e4daaad157189cbe9e2e10972d18f4219429aede14ad9cfb
Tx public key: f10f2daa777663687962bd191d02e048d6d15d6e3b6f386c9bcb1585d5adb2ed
Timestamp: 1723473845 Timestamp [UCT]: 2024-08-12 14:44:05 Age [y:d:h:m:s]: 00:234:11:29:22
Block: 1086352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167457 RingCT/type: yes/0
Extra: 01f10f2daa777663687962bd191d02e048d6d15d6e3b6f386c9bcb1585d5adb2ed021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6982b4d6cbb79781043385dfe5c54c02a863558fa145d4d3080a1f79cc264e3b 0.600000000000 1560949 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": 1086362, "vin": [ { "gen": { "height": 1086352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6982b4d6cbb79781043385dfe5c54c02a863558fa145d4d3080a1f79cc264e3b" } } ], "extra": [ 1, 241, 15, 45, 170, 119, 118, 99, 104, 121, 98, 189, 25, 29, 2, 224, 72, 214, 209, 93, 110, 59, 111, 56, 108, 155, 203, 21, 133, 213, 173, 178, 237, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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