← previous blocknext block →recent activity
Analyzing
Block #86,386,133
24 transactions · 22 stateful · 2026-07-08 10:02:52 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,386,133 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w18w29w314w015w116w217w318w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0xc5663f54…4df2
0x34b655…2a6f
6 touches
3 conflicts
0xfd5b3ee0…e36f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd16df6cd…5532
0x40c49f…2af0
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity