Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a171976155fd1826d2ef4f5b61cbd472b1eecda9e26d720da7a356f53af1f8b7

Tx prefix hash: afa11c89d800cd3b5596872c5ad824fe8240474fad4a19e0a6c7f0794e8a7a1c
Tx public key: 8575f856c55bb142941f718eac6727aa9bfdc8cbfd5d975d9105f45b132b69bd
Timestamp: 1715707733 Timestamp [UCT]: 2024-05-14 17:28:53 Age [y:d:h:m:s]: 00:329:23:02:48
Block: 1021970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235843 RingCT/type: yes/0
Extra: 018575f856c55bb142941f718eac6727aa9bfdc8cbfd5d975d9105f45b132b69bd02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f680eb1b56d47546028963a0d08e8d72ec0fc5ddd641890722daf975abdb464 0.600000000000 1486439 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": 1021980, "vin": [ { "gen": { "height": 1021970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f680eb1b56d47546028963a0d08e8d72ec0fc5ddd641890722daf975abdb464" } } ], "extra": [ 1, 133, 117, 248, 86, 197, 91, 177, 66, 148, 31, 113, 142, 172, 103, 39, 170, 155, 253, 200, 203, 253, 93, 151, 93, 145, 5, 244, 91, 19, 43, 105, 189, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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