← previous blocknext block →recent activity
Analyzing
Block #86,836,054
10 transactions · 10 stateful · 2026-07-10 12:11:52 UTC
Parallelism
40/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,836,054 · 10 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
2w03w14w27w38w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73a951a2…53db
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
4 touches
1 conflict
0x8d888c90…5479
0x34b655…2a6f
4 touches
1 conflict
0x8e507257…71c1
0x34b655…2a6f
4 touches
1 conflict
0xa1830b71…6cd6
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
3 conflicts on slot 0x73a951a2b6…c253db
Audit this contract →
← previous block·next block →recent activity