Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 984be57d830f403e6dbf01100a115814eb15938af893c8e0e6a59eef32e1ea54

Tx prefix hash: bb67cd4691da1438a452443c187bb038bab5c0da512210fb258850acb5cbd319
Tx public key: cd1e0d6a8b1943fa41ce4257849b8d92273f35ee3a87b0d556cad66fd449ecf4
Timestamp: 1710437049 Timestamp [UCT]: 2024-03-14 17:24:09 Age [y:d:h:m:s]: 00:319:01:58:21
Block: 978298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228134 RingCT/type: yes/0
Extra: 01cd1e0d6a8b1943fa41ce4257849b8d92273f35ee3a87b0d556cad66fd449ecf402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 908f0f046c7f6b8acd7fb2b8e40d17ab663421eb7435f36db91d0e490a9a0dba 0.600000000000 1438321 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": 978308, "vin": [ { "gen": { "height": 978298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "908f0f046c7f6b8acd7fb2b8e40d17ab663421eb7435f36db91d0e490a9a0dba" } } ], "extra": [ 1, 205, 30, 13, 106, 139, 25, 67, 250, 65, 206, 66, 87, 132, 155, 141, 146, 39, 63, 53, 238, 58, 135, 176, 213, 86, 202, 214, 111, 212, 73, 236, 244, 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