Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffd5060d85edfb25bea05e08f81b2accb95c58816f26dd0c8773f20f8fce0b7e

Tx prefix hash: 735b8c368b0ecd5657584a2c1770913a9283e406f71c47f29dd481ad1c7aed9f
Tx public key: f22a744ee9c3e50c56563a022c5d85d6145f673dd415e78ac096d8aba902ef3e
Timestamp: 1582097177 Timestamp [UTC]: 2020-02-19 07:26:17 Age [y:d:h:m:s]: 06:276:04:35:54
Block: 67864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1614809 RingCT/type: yes/0
Extra: 01f22a744ee9c3e50c56563a022c5d85d6145f673dd415e78ac096d8aba902ef3e021100000004026b59f3000000000000000000

1 output(s) for total of 0.365711993410 xmr

stealth address amount amount idx tag
00: 274738c59a03b6a0df3c8b590693efed8a0d327449f651154e55dedc6d1ab030 0.365711993410 125056 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": 67874, "vin": [ { "gen": { "height": 67864 } } ], "vout": [ { "amount": 365711993410, "target": { "key": "274738c59a03b6a0df3c8b590693efed8a0d327449f651154e55dedc6d1ab030" } } ], "extra": [ 1, 242, 42, 116, 78, 233, 195, 229, 12, 86, 86, 58, 2, 44, 93, 133, 214, 20, 95, 103, 61, 212, 21, 231, 138, 192, 150, 216, 171, 169, 2, 239, 62, 2, 17, 0, 0, 0, 4, 2, 107, 89, 243, 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: