Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef9b205dcf939751d028e4327244d282d73e0412f13157405a61864fb2aed087

Tx prefix hash: 0e4f92aed543a2c4bd61dbb30aaebab6fa2aa7d157c816bfadf62a1395b35a38
Tx public key: f897d2122e81e5b54ae8d31b279589a52f2b0b75ebac91fe4335cc67becd7e7a
Timestamp: 1593018773 Timestamp [UTC]: 2020-06-24 17:12:53 Age [y:d:h:m:s]: 06:148:21:41:11
Block: 110721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1571235 RingCT/type: yes/0
Extra: 01f897d2122e81e5b54ae8d31b279589a52f2b0b75ebac91fe4335cc67becd7e7a02110000007446a11e8a000000000000000000

1 output(s) for total of 0.263715776355 xmr

stealth address amount amount idx tag
00: 973fd893de75f59c2e96b7e041785013adca335a27b54d5efc44b738721313cb 0.263715776355 191609 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": 110731, "vin": [ { "gen": { "height": 110721 } } ], "vout": [ { "amount": 263715776355, "target": { "key": "973fd893de75f59c2e96b7e041785013adca335a27b54d5efc44b738721313cb" } } ], "extra": [ 1, 248, 151, 210, 18, 46, 129, 229, 181, 74, 232, 211, 27, 39, 149, 137, 165, 47, 43, 11, 117, 235, 172, 145, 254, 67, 53, 204, 103, 190, 205, 126, 122, 2, 17, 0, 0, 0, 116, 70, 161, 30, 138, 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: