Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf8dc40fb2d8ee1cd902434d57054fdeeebd2b24de9fe7afe4e0071b7b9dd541

Tx prefix hash: a70da44971a30c7f4044409ed623a5e9deab7273d169eb2ce6c84ced8303ad9a
Tx public key: 499fe700b219437ff8efb9813eb6c530a55a2d51d69bea6d4e2dcf928a20b968
Timestamp: 1771642989 Timestamp [UTC]: 2026-02-21 03:03:09 Age [y:d:h:m:s]: 00:269:23:29:26
Block: 1482354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198462 RingCT/type: yes/0
Extra: 01499fe700b219437ff8efb9813eb6c530a55a2d51d69bea6d4e2dcf928a20b968021100000009f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0b7ad077e63ce5e92aa5179d9f042f592677a6c623ff5917d53b0d5bc552292f 0.000600000000 1971746 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": 1482364, "vin": [ { "gen": { "height": 1482354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b7ad077e63ce5e92aa5179d9f042f592677a6c623ff5917d53b0d5bc552292f" } } ], "extra": [ 1, 73, 159, 231, 0, 178, 25, 67, 127, 248, 239, 185, 129, 62, 182, 197, 48, 165, 90, 45, 81, 214, 155, 234, 109, 78, 45, 207, 146, 138, 32, 185, 104, 2, 17, 0, 0, 0, 9, 241, 136, 200, 168, 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: