Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 644ea9d11f2f5123966cc2f8b39680fb2728f7c3af59ec1c707a0dd2ade58534

Tx prefix hash: 9bd43b1084a99e9639cacb37b0ae2d72438779aea633a7f75000d176321bd58f
Tx public key: f89f9aaa960a77d7b89e1d5e2362cae657b1719cecb4c3c1d94a4c048f4c4e09
Timestamp: 1694713793 Timestamp [UCT]: 2023-09-14 17:49:53 Age [y:d:h:m:s]: 01:243:13:13:34
Block: 848104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435190 RingCT/type: yes/0
Extra: 01f89f9aaa960a77d7b89e1d5e2362cae657b1719cecb4c3c1d94a4c048f4c4e0902110000000d4b8f5122000000000000000000

1 output(s) for total of 0.950340949000 dcy

stealth address amount amount idx
00: cb8e88dbb17f63001b77995866bd5b94dac20fb32ae431bf87309c402651fe1f 0.950340949000 1301688 of 0

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": 848114, "vin": [ { "gen": { "height": 848104 } } ], "vout": [ { "amount": 950340949, "target": { "key": "cb8e88dbb17f63001b77995866bd5b94dac20fb32ae431bf87309c402651fe1f" } } ], "extra": [ 1, 248, 159, 154, 170, 150, 10, 119, 215, 184, 158, 29, 94, 35, 98, 202, 230, 87, 177, 113, 156, 236, 180, 195, 193, 217, 74, 76, 4, 143, 76, 78, 9, 2, 17, 0, 0, 0, 13, 75, 143, 81, 34, 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