← previous blocknext block →recent activity
Analyzing
Block #87,716,011
30 transactions · 27 stateful · 2026-07-14 14:16:20 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,716,011 · 30 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
1w04w05w17w012w213w114w217w119w223w024w127w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf0e051a…10a0
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0xc8536f01…eb88
0x34b655…2a6f
6 touches
3 conflicts
0x5f234b05…db39
0x34b655…2a6f
6 touches
3 conflicts
0x4327afd2…1b3a
0x34b655…2a6f
4 touches
1 conflict
0x50b12cb9…edcd
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 0xbf0e051afa…7110a0
Audit this contract →
← previous block·next block →recent activity