← previous blocknext block →recent activity
Analyzing
Block #85,105,365
17 transactions · 16 stateful · 2026-07-02 11:43:25 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,105,365 · 17 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
4w05w16w29w211w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x678a8de3…7da5
0x34b655…2a6f
8 touches
6 conflicts
0x79b3209b…f766
0x34b655…2a6f
6 touches
3 conflicts
0x4c22021d…f8a7
0x34b655…2a6f
4 touches
1 conflict
0x58397d66…a6bc
0x34b655…2a6f
4 touches
1 conflict
0x5c0393a4…8b86
0x34b655…2a6f
4 touches
1 conflict
0xa148e75c…8114
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity