Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d279f2bcddbd4cb4698008933b855e719ef5ffd606a3d451403bdef1f8da1f3

Tx prefix hash: 2b0090300a538a2bfdd98be939c2b29df2ac556e8422e7f765edf95bb9ad32aa
Tx public key: 3bec2d4dfa20f4d9712ecd1b5910fbc3d9be01d083ee7c0e803c6fd0fe70abed
Timestamp: 1770897585 Timestamp [UTC]: 2026-02-12 11:59:45 Age [y:d:h:m:s]: 00:276:09:51:14
Block: 1476206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202979 RingCT/type: yes/0
Extra: 013bec2d4dfa20f4d9712ecd1b5910fbc3d9be01d083ee7c0e803c6fd0fe70abed021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 01f38cef0c883283acf27fc8cfd16c5bddc274c40555f14d5e4eb45ec27eac85 0.000600000000 1965510 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": 1476216, "vin": [ { "gen": { "height": 1476206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01f38cef0c883283acf27fc8cfd16c5bddc274c40555f14d5e4eb45ec27eac85" } } ], "extra": [ 1, 59, 236, 45, 77, 250, 32, 244, 217, 113, 46, 205, 27, 89, 16, 251, 195, 217, 190, 1, 208, 131, 238, 124, 14, 128, 60, 111, 208, 254, 112, 171, 237, 2, 17, 0, 0, 0, 5, 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: