← previous blocknext block →recent activity
Analyzing
Block #87,751,329
20 transactions · 19 stateful · 2026-07-14 18:12:40 UTC
Parallelism
75/100
Blocked
26%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,751,329 · 20 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
1w02w17w08w110w211w316w017w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f46250b…3bf2
0x34b655…2a6f
8 touches
6 conflicts
0xc57b566d…8591
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x463404f5…e861
0x34b655…2a6f
4 touches
1 conflict
0x463404f5…e862
0x34b655…2a6f
4 touches
1 conflict
0x4669b7d6…7790
0x34b655…2a6f
4 touches
1 conflict
0x6aa3c06e…c7d9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a2
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 0x6f46250b20…823bf2
Audit this contract →
← previous block·next block →recent activity