← previous blocknext block →recent activity
Analyzing
Block #86,836,000
13 transactions · 10 stateful · 2026-07-10 12:11:30 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,836,000 · 13 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
4w05w16w27w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d888c90…5479
0x34b655…2a6f
6 touches
3 conflicts
0xeeb38aa7…8f00
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xe2307994…acad
0x34b655…2a6f
4 touches
1 conflict
0x0a6ba3b4…2123
0x34b655…2a6f
4 touches
1 conflict
0x0c240a4e…9955
0x34b655…2a6f
4 touches
1 conflict
0x2003d8cf…6836
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 0x8d888c9003…aa5479
Audit this contract →
← previous block·next block →recent activity