← previous blocknext block →recent activity
Analyzing
Block #87,904,272
13 transactions · 13 stateful · 2026-07-15 11:15:41 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,904,272 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w38w410w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf28cf8dc…b0ca
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x224a9f90…3583
0x0a2fbf…29b1
4 touches
1 conflict
0x224a9f90…3586
0x0a2fbf…29b1
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0f6666e6…f280
0x34b655…2a6f
4 touches
1 conflict
0x44d24653…fa2f
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
6 conflicts on slot 0xf28cf8dcba…4ab0ca
Audit this contract →
← previous block·next block →recent activity