Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5faf2089caef08e74cf26dcb2aaff4a7cde3db0fa1aecb03bc43b8e842af32b4

Tx prefix hash: 28b117b3049d963113816ceb3c95151c61d4095f46384454e22f9403fc180dd6
Tx public key: 786bd7d3139e345b46a63f23ac2541ebe71d25d9bc0f43fb1c83dd889c1b53c7
Timestamp: 1761156422 Timestamp [UTC]: 2025-10-22 18:07:02 Age [y:d:h:m:s]: 01:030:20:04:34
Block: 1395651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287843 RingCT/type: yes/0
Extra: 01786bd7d3139e345b46a63f23ac2541ebe71d25d9bc0f43fb1c83dd889c1b53c70211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 10a94f85c545447869dc084322e88d7d704de0ba8d7c2d8c8af93f68de93c900 0.000600000000 1883934 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": 1395661, "vin": [ { "gen": { "height": 1395651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10a94f85c545447869dc084322e88d7d704de0ba8d7c2d8c8af93f68de93c900" } } ], "extra": [ 1, 120, 107, 215, 211, 19, 158, 52, 91, 70, 166, 63, 35, 172, 37, 65, 235, 231, 29, 37, 217, 188, 15, 67, 251, 28, 131, 221, 136, 156, 27, 83, 199, 2, 17, 0, 0, 0, 4, 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: