← previous blocknext block →recent activity
Analyzing
Block #86,321,024
27 transactions · 22 stateful · 2026-07-08 02:47:51 UTC
Parallelism
89/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,321,024 · 27 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w010w111w214w119w220w223w024w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x2dab27f5…2a4c
0x065c9d…c394
5 touches
3 conflicts
0xec5699ee…6a01
0xd32edf…ff58
5 touches
3 conflicts
0x7e2d46e0…388c
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf8f1e808…a4fd
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity