← previous blocknext block →recent activity
Analyzing
Block #87,724,200
16 transactions · 12 stateful · 2026-07-14 15:11:10 UTC
Parallelism
63/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,724,200 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w29w310w011w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd44476…ef40
0x34b655…2a6f
8 touches
6 conflicts
0x147259c6…1709
0x34b655…2a6f
8 touches
6 conflicts
0xcf5ef070…7d4f
0x34b655…2a6f
8 touches
6 conflicts
0x255ba9f3…396d
0x34b655…2a6f
4 touches
1 conflict
0x313d3d93…4aa2
0x34b655…2a6f
4 touches
1 conflict
0x3f93d576…f1de
0x34b655…2a6f
4 touches
1 conflict
0x4c64f524…1352
0x34b655…2a6f
4 touches
1 conflict
0x64800813…db9f
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 0x0dd44476b8…7fef40
Audit this contract →
← previous block·next block →recent activity