Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 119650d2e00d9f0d7ecd737b54d5bcaa4d44ec1b6cb90716b6186e25349ca3ad

Tx prefix hash: d7f9b8a6384e099ba9f4570896922436888b7c9a1d4751a84a17ea1477cba6e8
Tx public key: 8b660b3e524a110a73a0a4fd9be69ad229ba16bbacbc139a9eac48f657aafc86
Timestamp: 1700151837 Timestamp [UTC]: 2023-11-16 16:23:57 Age [y:d:h:m:s]: 02:176:17:39:20
Block: 893007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 638522 RingCT/type: yes/0
Extra: 018b660b3e524a110a73a0a4fd9be69ad229ba16bbacbc139a9eac48f657aafc8602110000000ee6d27f9c000000000000000000

1 output(s) for total of 0.000674678853 xmr

stealth address amount amount idx tag
00: 8fd37858a1c306938434ceb4c4cae36a482eadcb7e449bc6d962d131d7ea3d61 0.000674678853 1349170 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 dinastycoin-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": 893017, "vin": [ { "gen": { "height": 893007 } } ], "vout": [ { "amount": 674678853, "target": { "key": "8fd37858a1c306938434ceb4c4cae36a482eadcb7e449bc6d962d131d7ea3d61" } } ], "extra": [ 1, 139, 102, 11, 62, 82, 74, 17, 10, 115, 160, 164, 253, 155, 230, 154, 210, 41, 186, 22, 187, 172, 188, 19, 154, 158, 172, 72, 246, 87, 170, 252, 134, 2, 17, 0, 0, 0, 14, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: