Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7ada8998c36e0984e8cba1230e6b9b7fcc058f28798a9c8ce9ef3a00a52aab6

Tx prefix hash: ccfa193520552ca9e004ac5ce55c449203794dc84d5cdc6771a8e116a5768114
Tx public key: 9ee2ea2e47023df9f304bb2dbeb26019d54968d96ae3164cb006f8e40062606a
Timestamp: 1758630412 Timestamp [UTC]: 2025-09-23 12:26:52 Age [y:d:h:m:s]: 01:055:19:41:32
Block: 1374707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306283 RingCT/type: yes/0
Extra: 019ee2ea2e47023df9f304bb2dbeb26019d54968d96ae3164cb006f8e40062606a021100000005ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7a5cb974438d28bf6b5b9ca028a35983e15e547e5cd2bdff47c7459742bc308f 0.000600000000 1862792 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": 1374717, "vin": [ { "gen": { "height": 1374707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a5cb974438d28bf6b5b9ca028a35983e15e547e5cd2bdff47c7459742bc308f" } } ], "extra": [ 1, 158, 226, 234, 46, 71, 2, 61, 249, 243, 4, 187, 45, 190, 178, 96, 25, 213, 73, 104, 217, 106, 227, 22, 76, 176, 6, 248, 228, 0, 98, 96, 106, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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: