← previous blocknext block →recent activity
Analyzing
Block #94,972,871
18 transactions · 17 stateful · 2026-08-11 05:02:31 UTC
Parallelism
56/100
Blocked
59%
Avg conflicts / tx
1.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,972,871 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w513w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
16 touches
28 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x4c934202…ec09
0x851145…3f07
6 touches
3 conflicts
0x58d0a23c…5d3a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0x4deeee1b…8c0c
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
28 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity