Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f751ed5c18a1623ce64df5ffcb49fb3d002a6e19a15e1549de7700a47a1d93e

Tx prefix hash: ec081b8aa3c27a855efe44d54f7856a3259fc0b425e7c9cbfc1cf24b3badfda6
Tx public key: e17cd7158d75a70d71f741a66573777c00f6c135f716c8d9ed59214d28d99e48
Timestamp: 1696949383 Timestamp [UCT]: 2023-10-10 14:49:43 Age [y:d:h:m:s]: 01:104:09:03:11
Block: 866667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335808 RingCT/type: yes/0
Extra: 01e17cd7158d75a70d71f741a66573777c00f6c135f716c8d9ed59214d28d99e48021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.824845274000 dcy

stealth address amount amount idx
00: 89eacbdb2c7bd3f304f7deadcab9b4231926719705b5b5cc46d5add3bc0765e0 0.824845274000 1321289 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": 866677, "vin": [ { "gen": { "height": 866667 } } ], "vout": [ { "amount": 824845274, "target": { "key": "89eacbdb2c7bd3f304f7deadcab9b4231926719705b5b5cc46d5add3bc0765e0" } } ], "extra": [ 1, 225, 124, 215, 21, 141, 117, 167, 13, 113, 247, 65, 166, 101, 115, 119, 124, 0, 246, 193, 53, 247, 22, 200, 217, 237, 89, 33, 77, 40, 217, 158, 72, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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