Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af61a244cd2ee79581ed894518ebd4acc2e277dc8d9a3013c35fb282745f747d

Tx prefix hash: 62c602897df4fd64f2312be40327b69b1c290183d28b9c2d890915c570de9fff
Tx public key: daacab1e8082bcbfc9b255d7f6799f610ac18491c488216c7cbafeb9b2c82188
Timestamp: 1737155335 Timestamp [UCT]: 2025-01-17 23:08:55 Age [y:d:h:m:s]: 00:058:13:18:22
Block: 1199629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41640 RingCT/type: yes/0
Extra: 01daacab1e8082bcbfc9b255d7f6799f610ac18491c488216c7cbafeb9b2c821880211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8f598891b1e3123b16310c15dcda06a02d3997afc58b947c2c0fe3c001f1957 0.600000000000 1686262 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": 1199639, "vin": [ { "gen": { "height": 1199629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8f598891b1e3123b16310c15dcda06a02d3997afc58b947c2c0fe3c001f1957" } } ], "extra": [ 1, 218, 172, 171, 30, 128, 130, 188, 191, 201, 178, 85, 215, 246, 121, 159, 97, 10, 193, 132, 145, 196, 136, 33, 108, 124, 186, 254, 185, 178, 200, 33, 136, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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