Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8080d2c2c0922cb9c64f151b8b0ac97755d5835fbdac4cf627111bae545dac0

Tx prefix hash: 62d9b78f1f42d1364afcc341690809cc208486c5bb9a31d17d262ba4895e7840
Tx public key: 0fbdbad07d28d1751e0797459bd7a7755fcaa832c87a083ed392f7d0f42eac8c
Timestamp: 1733068407 Timestamp [UCT]: 2024-12-01 15:53:27 Age [y:d:h:m:s]: 00:121:04:28:33
Block: 1165804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86397 RingCT/type: yes/0
Extra: 010fbdbad07d28d1751e0797459bd7a7755fcaa832c87a083ed392f7d0f42eac8c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a86f50c687afa317459b4cba7d2b0e4d2f47e65497155b513accb7b19c1b102f 0.600000000000 1651479 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": 1165814, "vin": [ { "gen": { "height": 1165804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a86f50c687afa317459b4cba7d2b0e4d2f47e65497155b513accb7b19c1b102f" } } ], "extra": [ 1, 15, 189, 186, 208, 125, 40, 209, 117, 30, 7, 151, 69, 155, 215, 167, 117, 95, 202, 168, 50, 200, 122, 8, 62, 211, 146, 247, 208, 244, 46, 172, 140, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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