Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0e35ea846d98c0b2a84225f5c84cdd9179633e3d03bfc11201cbf204bd0cf16

Tx prefix hash: 1380a62891ab2b7d7b0e45d8504c3ca2eab8e6693877aca81d02a7724b571d34
Tx public key: c24aa142602bafd38b7c40045f41b81805413c06e9f428a8e1b016b8d352e557
Timestamp: 1719397678 Timestamp [UCT]: 2024-06-26 10:27:58 Age [y:d:h:m:s]: 00:264:02:04:44
Block: 1052552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188718 RingCT/type: yes/0
Extra: 01c24aa142602bafd38b7c40045f41b81805413c06e9f428a8e1b016b8d352e55702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c002014ec981948f2b38e1440b1217cc713e8b4a9b31cadd2d28746e7489dd8f 0.600000000000 1522881 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": 1052562, "vin": [ { "gen": { "height": 1052552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c002014ec981948f2b38e1440b1217cc713e8b4a9b31cadd2d28746e7489dd8f" } } ], "extra": [ 1, 194, 74, 161, 66, 96, 43, 175, 211, 139, 124, 64, 4, 95, 65, 184, 24, 5, 65, 60, 6, 233, 244, 40, 168, 225, 176, 22, 184, 211, 82, 229, 87, 2, 17, 0, 0, 0, 4, 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