Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ff25920b79cd0b4b820c61e0cd6bb87e448933ef5f9122296598142c7cc99c8

Tx prefix hash: c819b3bd9c20a5e1a458c55732ac46ed28a524bca7a9cb8acd90ccc2821492f9
Tx public key: 5160546e56f73317136bd5975642de33edc5d55f434e548e9bf2dc6ce1116524
Timestamp: 1742923246 Timestamp [UTC]: 2025-03-25 17:20:46 Age [y:d:h:m:s]: 01:238:06:18:42
Block: 1247116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434365 RingCT/type: yes/0
Extra: 015160546e56f73317136bd5975642de33edc5d55f434e548e9bf2dc6ce1116524021100000008c6740958000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f122c9a58353970d13a1a82a7c8de113d0309e34a4709c0aee153bed959c0e00 0.000600000000 1734117 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": 1247126, "vin": [ { "gen": { "height": 1247116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f122c9a58353970d13a1a82a7c8de113d0309e34a4709c0aee153bed959c0e00" } } ], "extra": [ 1, 81, 96, 84, 110, 86, 247, 51, 23, 19, 107, 213, 151, 86, 66, 222, 51, 237, 197, 213, 95, 67, 78, 84, 142, 155, 242, 220, 108, 225, 17, 101, 36, 2, 17, 0, 0, 0, 8, 198, 116, 9, 88, 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: