Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f5b52f28bbe1153a18f24394c29a832d48e5bbfe8f200dcfe282f9dcbb4d9db

Tx prefix hash: 63596be8fac043d30e4dbe96ecf959e7dc187db803dbb560334cc31ddf4b19c2
Tx public key: 4c2d555ffabad4091eab80ec9ff4a982af6e4484bb3053c75fe0feb7e888f7a3
Timestamp: 1771453293 Timestamp [UTC]: 2026-02-18 22:21:33 Age [y:d:h:m:s]: 00:271:04:00:55
Block: 1480776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199301 RingCT/type: yes/0
Extra: 014c2d555ffabad4091eab80ec9ff4a982af6e4484bb3053c75fe0feb7e888f7a3021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c18e6cd5ace41c2d30c2a08b6874c413c413ca199504dcd6e8e2492eefa572bf 0.000600000000 1970146 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": 1480786, "vin": [ { "gen": { "height": 1480776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c18e6cd5ace41c2d30c2a08b6874c413c413ca199504dcd6e8e2492eefa572bf" } } ], "extra": [ 1, 76, 45, 85, 95, 250, 186, 212, 9, 30, 171, 128, 236, 159, 244, 169, 130, 175, 110, 68, 132, 187, 48, 83, 199, 95, 224, 254, 183, 232, 136, 247, 163, 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: