← previous blocknext block →recent activity
Analyzing
Block #87,262,939
18 transactions · 17 stateful · 2026-07-12 11:45:38 UTC
Parallelism
56/100
Blocked
41%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,262,939 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w38w49w511w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x0dd44476…ef40
0x34b655…2a6f
12 touches
15 conflicts
0xc05939be…c684
0x34b655…2a6f
8 touches
6 conflicts
0xbd6e61f7…3ede
0x34b655…2a6f
8 touches
6 conflicts
0x3f4d2f3d…d3b8
0x34b655…2a6f
8 touches
6 conflicts
0x3f4d2f3d…d3b9
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity