Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 561302339a8e3cbe36d992af83d3e613edd53f8b7bfc86f2bfad67580a08ce87

Tx prefix hash: 603a25303c475ddbdb2377f5fcb2f7d205b98a4f8bf5d1f131c7a47cd0438dd8
Tx public key: c96f9b1697c407abebc4e5dacdd1a6d35cf863e14f4f5713c84b8577ed63ea69
Timestamp: 1788814562 Timestamp [UTC]: 2026-09-07 20:56:02 Age [y:d:h:m:s]: 00:076:01:58:45
Block: 1630437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 53713 RingCT/type: yes/0
Extra: 01c96f9b1697c407abebc4e5dacdd1a6d35cf863e14f4f5713c84b8577ed63ea69

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ffce61c0e1b4b3dc3af5e50b9b94db8c7d24d9df2808ab04c33eab0af00f7237 0.000600000000 2120457 of 15 <8e>

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": 1630447, "vin": [ { "gen": { "height": 1630437 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "ffce61c0e1b4b3dc3af5e50b9b94db8c7d24d9df2808ab04c33eab0af00f7237", "view_tag": "8e" } } } ], "extra": [ 1, 201, 111, 155, 22, 151, 196, 7, 171, 235, 196, 229, 218, 205, 209, 166, 211, 92, 248, 99, 225, 79, 79, 87, 19, 200, 75, 133, 119, 237, 99, 234, 105 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: