← previous blocknext block →recent activity
Analyzing
Block #85,136,140
12 transactions · 12 stateful · 2026-07-02 15:09:10 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,136,140 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd893f34f…bdd2
0x34b655…2a6f
8 touches
6 conflicts
0xee778d11…3eaa
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x11d4f8d4…6e3f
0x34b655…2a6f
8 touches
6 conflicts
0x366f651e…6100
0x34b655…2a6f
8 touches
6 conflicts
0xe47478a3…a058
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x510e66b1…aef7
0x34b655…2a6f
8 touches
6 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 0xd893f34f22…4dbdd2
Audit this contract →
← previous block·next block →recent activity