← previous blocknext block →recent activity
Analyzing
Block #87,727,220
17 transactions · 16 stateful · 2026-07-14 15:31:24 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,727,220 · 17 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
2w03w15w06w110w211w012w113w214w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x26b1c9ae…93f9
0x0a2fbf…29b1
6 touches
3 conflicts
0x26b1c9ae…93fa
0x0a2fbf…29b1
6 touches
3 conflicts
0x9b489631…4447
0x0a2fbf…29b1
6 touches
3 conflicts
0x9b489631…4448
0x0a2fbf…29b1
6 touches
3 conflicts
0x9b489631…444b
0x0a2fbf…29b1
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity