Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e3103975d7a86eb7357b7db4a2c86306c5b67ca43827d7f8cce3eaa8c89bea

Tx prefix hash: 0bbd9c22c5cfdea10a894cb016be6617ef8fd1e50f16351005e8c2e3d1816d2e
Tx public key: ea9c507902b35af4cf45e2f80be84f3b7889a3a7d85ca5d3d9251786a627798d
Timestamp: 1708198173 Timestamp [UCT]: 2024-02-17 19:29:33 Age [y:d:h:m:s]: 01:096:04:47:17
Block: 959706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329832 RingCT/type: yes/0
Extra: 01ea9c507902b35af4cf45e2f80be84f3b7889a3a7d85ca5d3d9251786a627798d02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68f7c2c2ab623d7d0b82d4e63aab03a478ce8c2fcc53f0efeb7839e80773fcc5 0.600000000000 1419259 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": 959716, "vin": [ { "gen": { "height": 959706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68f7c2c2ab623d7d0b82d4e63aab03a478ce8c2fcc53f0efeb7839e80773fcc5" } } ], "extra": [ 1, 234, 156, 80, 121, 2, 179, 90, 244, 207, 69, 226, 248, 11, 232, 79, 59, 120, 137, 163, 167, 216, 92, 165, 211, 217, 37, 23, 134, 166, 39, 121, 141, 2, 17, 0, 0, 0, 5, 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