← previous blocknext block →recent activity
Analyzing
Block #86,987,335
15 transactions · 14 stateful · 2026-07-11 05:02:58 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,987,335 · 15 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
4w05w07w19w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2ce91e2…b99e
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xb6ed530c…d450
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x28fc8829…a870
0x34b655…2a6f
4 touches
1 conflict
0x36638a70…343b
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
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 0xe2ce91e233…5eb99e
Audit this contract →
← previous block·next block →recent activity