← previous blocknext block →recent activity
Analyzing
Block #87,327,611
12 transactions · 12 stateful · 2026-07-12 18:58:03 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,327,611 · 12 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
2w05w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b413174…92b9
0x34b655…2a6f
4 touches
1 conflict
0x8b413174…92ba
0x34b655…2a6f
4 touches
1 conflict
0x1cf8164f…01bf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc6244378…2a14
0x34b655…2a6f
4 touches
1 conflict
0x3093e806…bde2
0x34b655…2a6f
2 touches
0 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
2 touches
0 conflicts
0x76ebf9c2…e0ef
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 0x8b41317444…2892b9
Audit this contract →
← previous block·next block →recent activity