← previous blocknext block →recent activity
Analyzing
Block #86,807,396
23 transactions · 20 stateful · 2026-07-10 09:00:05 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,807,396 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w111w213w314w415w016w117w221w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x30643e3a…dc6f
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x5a36d0c8…12e3
0x34b655…2a6f
4 touches
1 conflict
0x7017d770…abbd
0x34b655…2a6f
4 touches
1 conflict
0x7017d770…abbe
0x34b655…2a6f
4 touches
1 conflict
0x85c84f98…06d7
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity