Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e21db0f7244be4b52cef74eb4c1cf53a4a48f0aeacc1ebcd56aaf655ff3199c

Tx prefix hash: f805eed3bfd70d28e19f5e5ff333553c3eb2201b7ed076a7702cd0107d89c384
Tx public key: 2f5f74f860d9823e41664acafa1b41ec7d7bc2552fe78ad8ed748509af02c3fe
Timestamp: 1765394824 Timestamp [UTC]: 2025-12-10 19:27:04 Age [y:d:h:m:s]: 00:346:15:36:32
Block: 1430765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252729 RingCT/type: yes/0
Extra: 012f5f74f860d9823e41664acafa1b41ec7d7bc2552fe78ad8ed748509af02c3fe02110000000270609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 295bb2e5de2c07925a4e364fbbac50694734ae3c6c20355f7945ed123723fb10 0.000600000000 1919518 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": 1430775, "vin": [ { "gen": { "height": 1430765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "295bb2e5de2c07925a4e364fbbac50694734ae3c6c20355f7945ed123723fb10" } } ], "extra": [ 1, 47, 95, 116, 248, 96, 217, 130, 62, 65, 102, 74, 202, 250, 27, 65, 236, 125, 123, 194, 85, 47, 231, 138, 216, 237, 116, 133, 9, 175, 2, 195, 254, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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: