Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438d7092937e3a4c3f98dccd3cd43bef3d0aceedeee770af16bcd33daf60bc6e

Tx prefix hash: d0137f74ff9c5e0e42c76e86697c33afd208555d6b7f06842e871bfddfadd83e
Tx public key: 9f7cb2857a0fe8f4efb8366136485164cb16ca8144db81e29de428ea13a04025
Timestamp: 1657375765 Timestamp [UCT]: 2022-07-09 14:09:25 Age [y:d:h:m:s]: 02:180:13:56:43
Block: 540081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 650407 RingCT/type: yes/0
Extra: 019f7cb2857a0fe8f4efb8366136485164cb16ca8144db81e29de428ea13a0402502110000000dc9067537000000000000000000

1 output(s) for total of 9.965236166000 dcy

stealth address amount amount idx
00: b50674e5b07bb39c81319550bc3c3c55710bcd25ec43b6f2761f14cb9fcfb873 9.965236166000 970276 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": 540091, "vin": [ { "gen": { "height": 540081 } } ], "vout": [ { "amount": 9965236166, "target": { "key": "b50674e5b07bb39c81319550bc3c3c55710bcd25ec43b6f2761f14cb9fcfb873" } } ], "extra": [ 1, 159, 124, 178, 133, 122, 15, 232, 244, 239, 184, 54, 97, 54, 72, 81, 100, 203, 22, 202, 129, 68, 219, 129, 226, 157, 228, 40, 234, 19, 160, 64, 37, 2, 17, 0, 0, 0, 13, 201, 6, 117, 55, 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