Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379ce9a1830d4100d8e89297e7357f0a6f7da604c2293015bdd831bd7afd0bfa

Tx prefix hash: 1051a79816f4a94ff82ef24806a3ef981b1ff1cdef1dcdd00f0110ab89158c26
Tx public key: b1afcd00d2faedd18114e6f06719b0fb99e36896b7445ff854b39752255daf01
Timestamp: 1712324947 Timestamp [UTC]: 2024-04-05 13:49:07 Age [y:d:h:m:s]: 02:039:16:47:07
Block: 993896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540282 RingCT/type: yes/0
Extra: 01b1afcd00d2faedd18114e6f06719b0fb99e36896b7445ff854b39752255daf0102110000000659dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 74af14c3e34e6d5c3e8cf91f731a048fed41f4bd20d2578a8c6f65a6adebf918 0.000600000000 1454292 of 15 -

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": 993906, "vin": [ { "gen": { "height": 993896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74af14c3e34e6d5c3e8cf91f731a048fed41f4bd20d2578a8c6f65a6adebf918" } } ], "extra": [ 1, 177, 175, 205, 0, 210, 250, 237, 209, 129, 20, 230, 240, 103, 25, 176, 251, 153, 227, 104, 150, 183, 68, 95, 248, 84, 179, 151, 82, 37, 93, 175, 1, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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: