← previous blocknext block →recent activity
Analyzing
Block #86,335,344
9 transactions · 8 stateful · 2026-07-08 04:23:28 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,335,344 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x213a507d…eb5f
0x34b655…2a6f
3 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
2 touches
0 conflicts
0x503b3a72…f6df
0x34b655…2a6f
2 touches
0 conflicts
0x596b0c48…ab66
0x34b655…2a6f
2 touches
0 conflicts
0x72fd59f1…b722
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity