← previous blocknext block →recent activity
Analyzing
Block #94,752,791
19 transactions · 18 stateful · 2026-08-10 10:35:22 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,752,791 · 19 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
1w03w04w05w16w27w38w39w410w012w113w214w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4f9cac7…fd98
0x34b655…2a6f
8 touches
6 conflicts
0x103be197…826c
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x56e254bc…1215
0x34b655…2a6f
6 touches
3 conflicts
0x5ad8cde9…f612
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2db
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…7215
0x34b655…2a6f
6 touches
3 conflicts
0xacca1d4f…d6df
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xf4f9cac7d9…09fd98
Audit this contract →
← previous block·next block →recent activity