← previous blocknext block →recent activity
Analyzing
Block #87,910,931
23 transactions · 20 stateful · 2026-07-15 12:00:13 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,910,931 · 23 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
4w06w17w28w012w114w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06a27525…f082
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x72880226…1435
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xe63a9ab2…a44f
0x34b655…2a6f
4 touches
1 conflict
0x2000b734…5e5a
0x34b655…2a6f
4 touches
1 conflict
0x27f0179f…15fe
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e2
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
3 conflicts on slot 0x06a2752594…3af082
Audit this contract →
← previous block·next block →recent activity