← previous blocknext block →recent activity
Analyzing
Block #87,787,013
20 transactions · 17 stateful · 2026-07-14 22:11:23 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,787,013 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w110w214w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd50d8366…df9c
0x34b655…2a6f
4 touches
1 conflict
0xd50d8366…df9d
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0d42a59b…df19
0x34b655…2a6f
4 touches
1 conflict
0x17c73702…674c
0x34b655…2a6f
4 touches
1 conflict
0x2e283bef…e2c0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
1 conflict on slot 0xd50d836695…72df9c
Audit this contract →
← previous block·next block →recent activity