Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40ba5b0f34477aef9f0eec40507c564ffe1324a71e727d02fab0f71e62c3a302

Tx prefix hash: 0432f0aee55ba09dc45ca516b2b7906d9e989dd7eeca8b987ad1a9c24353b9eb
Tx public key: dd2683bd4bfa11619fd531c8bf05ef88b98a6e835d6d0ae6c181e420c2708aa5
Timestamp: 1761304469 Timestamp [UTC]: 2025-10-24 11:14:29 Age [y:d:h:m:s]: 01:026:13:40:51
Block: 1396883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285395 RingCT/type: yes/0
Extra: 01dd2683bd4bfa11619fd531c8bf05ef88b98a6e835d6d0ae6c181e420c2708aa50211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7509d26dd946babba06987a6c59e8fb80cdad852c2ef2e1aa6c8aa3c777d6b1f 0.000600000000 1885170 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": 1396893, "vin": [ { "gen": { "height": 1396883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7509d26dd946babba06987a6c59e8fb80cdad852c2ef2e1aa6c8aa3c777d6b1f" } } ], "extra": [ 1, 221, 38, 131, 189, 75, 250, 17, 97, 159, 213, 49, 200, 191, 5, 239, 136, 185, 138, 110, 131, 93, 109, 10, 230, 193, 129, 228, 32, 194, 112, 138, 165, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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: