Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dae2d340bbb407cf24e030f2524f22dabb7805c7cb2ddf5061cd0306f2b89ae

Tx prefix hash: 43f5e9ccb7f7c1980689ea0873ec4a6bd39e6d252605bcde6df80949cc1d12fc
Tx public key: 1cc3c397231dca4ad040f859b8ea61834c47b86d3ab32067a5f10c0899b635bf
Timestamp: 1774075823 Timestamp [UTC]: 2026-03-21 06:50:23 Age [y:d:h:m:s]: 00:239:09:25:00
Block: 1502462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176553 RingCT/type: yes/0
Extra: 011cc3c397231dca4ad040f859b8ea61834c47b86d3ab32067a5f10c0899b635bf021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 16fd643b3fd3e5acc2c8ef013a755135e80785f10b0ecfb5b731343e88a0ee7c 0.000600000000 1992160 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": 1502472, "vin": [ { "gen": { "height": 1502462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16fd643b3fd3e5acc2c8ef013a755135e80785f10b0ecfb5b731343e88a0ee7c" } } ], "extra": [ 1, 28, 195, 195, 151, 35, 29, 202, 74, 208, 64, 248, 89, 184, 234, 97, 131, 76, 71, 184, 109, 58, 179, 32, 103, 165, 241, 12, 8, 153, 182, 53, 191, 2, 17, 0, 0, 0, 3, 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: