← previous blocknext block →recent activity
Analyzing
Block #94,739,360
10 transactions · 10 stateful · 2026-08-10 09:26:55 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,739,360 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f203394…f2dc
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0xd5ce83e2…b508
0x34b655…2a6f
3 touches
1 conflict
0x9cab73f3…a972
0x34b655…2a6f
3 touches
1 conflict
0x454cdf57…aebc
0x34b655…2a6f
2 touches
0 conflicts
0x579d249f…4b43
0x34b655…2a6f
2 touches
0 conflicts
0x5f46663c…b4c2
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x8f2033941d…ebf2dc
Audit this contract →
← previous block·next block →recent activity