Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7163a55c7883f7bd92e42978e0cb3452b36e5846e16663697d9ca5e8173e6a0e

Tx prefix hash: 347698f3e8f1ad6a290dcf19ea47843ae71a1c68b1991f231bbbd709f1e85871
Tx public key: 77abdb8dbf9d02763d89929eca5caa839309bf31d02e638241d9d1eb987a052a
Timestamp: 1697272843 Timestamp [UCT]: 2023-10-14 08:40:43 Age [y:d:h:m:s]: 02:050:18:27:22
Block: 869339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555932 RingCT/type: yes/0
Extra: 0177abdb8dbf9d02763d89929eca5caa839309bf31d02e638241d9d1eb987a052a02110000000633af99f4000000000000000000

1 output(s) for total of 0.808200364000 dcy

stealth address amount amount idx
00: d6f8cc30fd0523cae3997dcd21f9d9d3784d0bbfc3547349f789755d5edd9dc6 0.808200364000 1324180 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": 869349, "vin": [ { "gen": { "height": 869339 } } ], "vout": [ { "amount": 808200364, "target": { "key": "d6f8cc30fd0523cae3997dcd21f9d9d3784d0bbfc3547349f789755d5edd9dc6" } } ], "extra": [ 1, 119, 171, 219, 141, 191, 157, 2, 118, 61, 137, 146, 158, 202, 92, 170, 131, 147, 9, 191, 49, 208, 46, 99, 130, 65, 217, 209, 235, 152, 122, 5, 42, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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