Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d11fff6c4256fbd51eabd906044b47bd7e8346f4bdd7cf9d0a0853a83803fa3

Tx prefix hash: 294a0a2321a81ef41ca745b2a33b352254c13a4bb43efc4c88be30309cf78b70
Tx public key: e7cd9d841277edbff0710e8299e8c19fcfea212c8cc888ac92dc8f5a3bbd9be3
Timestamp: 1771951440 Timestamp [UTC]: 2026-02-24 16:44:00 Age [y:d:h:m:s]: 00:076:22:47:15
Block: 1484913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47285 RingCT/type: yes/0
Extra: 01e7cd9d841277edbff0710e8299e8c19fcfea212c8cc888ac92dc8f5a3bbd9be3021100000009e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1c508522aa619584cbe2eb9d62ae8662bfa755a2fd8470ef9535e873efdb63e2 0.000600000000 1974345 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": 1484923, "vin": [ { "gen": { "height": 1484913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c508522aa619584cbe2eb9d62ae8662bfa755a2fd8470ef9535e873efdb63e2" } } ], "extra": [ 1, 231, 205, 157, 132, 18, 119, 237, 191, 240, 113, 14, 130, 153, 232, 193, 159, 207, 234, 33, 44, 140, 200, 136, 172, 146, 220, 143, 90, 59, 189, 155, 227, 2, 17, 0, 0, 0, 9, 228, 245, 25, 63, 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: