Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 687b22a059cfb2ac150fb500859fc488584507a1652d7dace56c0bee4d6c8fe2

Tx prefix hash: 91fb36925904096eff5ff4833d46d94e05b5ef9f8d0892c3f6fb0bb41678cf0f
Tx public key: 96acbcbc930b79c7f8e1ef1f41849d7798b3b7983700dd8988f459c4042771b4
Timestamp: 1696144900 Timestamp [UCT]: 2023-10-01 07:21:40 Age [y:d:h:m:s]: 01:108:01:43:40
Block: 859987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338510 RingCT/type: yes/0
Extra: 0196acbcbc930b79c7f8e1ef1f41849d7798b3b7983700dd8988f459c4042771b4021100000009faf35c9c000000000000000000

1 output(s) for total of 0.867972795000 dcy

stealth address amount amount idx
00: 3d343f0453589f0962c2eaeb1064363d78487e8ea8cf95383922c7b78b3df687 0.867972795000 1314243 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": 859997, "vin": [ { "gen": { "height": 859987 } } ], "vout": [ { "amount": 867972795, "target": { "key": "3d343f0453589f0962c2eaeb1064363d78487e8ea8cf95383922c7b78b3df687" } } ], "extra": [ 1, 150, 172, 188, 188, 147, 11, 121, 199, 248, 225, 239, 31, 65, 132, 157, 119, 152, 179, 183, 152, 55, 0, 221, 137, 136, 244, 89, 196, 4, 39, 113, 180, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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