← previous blocknext block →recent activity
Analyzing
Block #94,840,425
18 transactions · 18 stateful · 2026-08-10 17:56:22 UTC
Parallelism
67/100
Blocked
61%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,840,425 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w410w211w412w213w115w217w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
6 touches
3 conflicts
0x6d9ac479…9276
0x34b655…2a6f
4 touches
1 conflict
0x92ba05e6…f85c
0x34b655…2a6f
4 touches
1 conflict
0x98862f54…62ca
0x34b655…2a6f
4 touches
1 conflict
0x98a1bad6…5130
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity