← previous blocknext block →recent activity
Analyzing
Block #86,664,533
12 transactions · 9 stateful · 2026-07-09 17:06:04 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,664,533 · 12 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
5w07w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5a9274d…78d7
0x34b655…2a6f
4 touches
1 conflict
0x51ace429…e7b7
0x065c9d…c394
2 touches
0 conflicts
0x7fa9697d…598a
0x065c9d…c394
2 touches
0 conflicts
0xa9f633f5…7480
0x065c9d…c394
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 0x1d351a9b20…2df2dd
Audit this contract →
← previous block·next block →recent activity