Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c1238d0722c0fcab5a9efd7d8ccb4b350fa58ae408298b71ed0a1cab8d8255d

Tx prefix hash: a6ad59cffcabd270f6a8bf1a3421d9877740699f12ff403ce90ca4959c90496c
Tx public key: 21f9e0b1ccb81b5b4c30b8064a8400ec9058695e3c19ce8bd2461ad1883c6593
Timestamp: 1726839741 Timestamp [UCT]: 2024-09-20 13:42:21 Age [y:d:h:m:s]: 00:113:23:56:58
Block: 1114263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81513 RingCT/type: yes/0
Extra: 0121f9e0b1ccb81b5b4c30b8064a8400ec9058695e3c19ce8bd2461ad1883c659302110000000abdafe9cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8a326d4f1b4125790a5fff7b71ccffed9694a10e03a9e90c7da3237aca7b73a 0.600000000000 1594062 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": 1114273, "vin": [ { "gen": { "height": 1114263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a326d4f1b4125790a5fff7b71ccffed9694a10e03a9e90c7da3237aca7b73a" } } ], "extra": [ 1, 33, 249, 224, 177, 204, 184, 27, 91, 76, 48, 184, 6, 74, 132, 0, 236, 144, 88, 105, 94, 60, 25, 206, 139, 210, 70, 26, 209, 136, 60, 101, 147, 2, 17, 0, 0, 0, 10, 189, 175, 233, 204, 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