Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a62c1ea93dcb3461291defb38584cd09298d7e5c2fefd9e504973e4f004b70c

Tx prefix hash: 263112001f2c2054e816e970933a994950d870507ddc4079229270de58ab399d
Tx public key: 270b1fb44b7c3cd3f8f89194f6b0f1beb01cbd53289fa85ad7e5dab02957f03b
Timestamp: 1774406330 Timestamp [UTC]: 2026-03-25 02:38:50 Age [y:d:h:m:s]: 00:237:11:02:06
Block: 1505209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175202 RingCT/type: yes/0
Extra: 01270b1fb44b7c3cd3f8f89194f6b0f1beb01cbd53289fa85ad7e5dab02957f03b021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf3973b0b4ff11e6f3ac2dae5490ce1ab0edb214c6b003b7f0a9d1a9de0a9330 0.000600000000 1994941 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": 1505219, "vin": [ { "gen": { "height": 1505209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf3973b0b4ff11e6f3ac2dae5490ce1ab0edb214c6b003b7f0a9d1a9de0a9330" } } ], "extra": [ 1, 39, 11, 31, 180, 75, 124, 60, 211, 248, 248, 145, 148, 246, 176, 241, 190, 176, 28, 189, 83, 40, 159, 168, 90, 215, 229, 218, 176, 41, 87, 240, 59, 2, 17, 0, 0, 0, 7, 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: