← previous blocknext block →recent activity
Analyzing
Block #87,064,319
11 transactions · 8 stateful · 2026-07-11 13:37:20 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,064,319 · 11 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c53719e…0366
0x34b655…2a6f
4 touches
1 conflict
0x25f0d803…174e
0x34b655…2a6f
4 touches
1 conflict
0x79e5df76…64ee
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd1952ceb…56be
0x34b655…2a6f
4 touches
1 conflict
0x016aa3dc…f1da
0x34b655…2a6f
2 touches
0 conflicts
0x03441b14…d8fd
0x34b655…2a6f
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 0x0c53719e11…2e0366
Audit this contract →
← previous block·next block →recent activity