Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d7674fd4e0bd6653a76b7e2cc64031def80de68e474d291fe4f520ccf359ad0

Tx prefix hash: 6969fa9b0ccc38cb3fea9508e7c63069f4fa716a8eba14592687612fa2dc601a
Tx public key: 3b08fedfdd6606ec744432367780dc55c07134ae3765cf6c3dc84004f524ffdf
Timestamp: 1761216746 Timestamp [UTC]: 2025-10-23 10:52:26 Age [y:d:h:m:s]: 01:026:09:28:45
Block: 1396150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285214 RingCT/type: yes/0
Extra: 013b08fedfdd6606ec744432367780dc55c07134ae3765cf6c3dc84004f524ffdf0211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5de6df1613181623d021e29b55cce7c018063feb4f82f37dfe39e9530424b8d5 0.000600000000 1884435 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": 1396160, "vin": [ { "gen": { "height": 1396150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5de6df1613181623d021e29b55cce7c018063feb4f82f37dfe39e9530424b8d5" } } ], "extra": [ 1, 59, 8, 254, 223, 221, 102, 6, 236, 116, 68, 50, 54, 119, 128, 220, 85, 192, 113, 52, 174, 55, 101, 207, 108, 61, 200, 64, 4, 245, 36, 255, 223, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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: