Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caf3b252d5750126386c44016b90caf699036f8783b897f21d15620e7ea9a3f2

Tx prefix hash: 8547acee8974d6a15885d6316bd381f6957bdaf3fbc86496a91ce5c82e6db5dc
Tx public key: 0cb0956c2edd4a1411908fc34a2cbce2b8d2056c5b863b6317b49c0a3920d712
Timestamp: 1721413725 Timestamp [UCT]: 2024-07-19 18:28:45 Age [y:d:h:m:s]: 00:264:09:59:04
Block: 1069283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188893 RingCT/type: yes/0
Extra: 010cb0956c2edd4a1411908fc34a2cbce2b8d2056c5b863b6317b49c0a3920d71202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e67bf8c1078456dc58acd4620cd081d3fc240aa1ee75ae53512de0b8c4324501 0.600000000000 1540652 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": 1069293, "vin": [ { "gen": { "height": 1069283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e67bf8c1078456dc58acd4620cd081d3fc240aa1ee75ae53512de0b8c4324501" } } ], "extra": [ 1, 12, 176, 149, 108, 46, 221, 74, 20, 17, 144, 143, 195, 74, 44, 188, 226, 184, 210, 5, 108, 91, 134, 59, 99, 23, 180, 156, 10, 57, 32, 215, 18, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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