← previous blocknext block →recent activity
Analyzing
Block #87,583,940
16 transactions · 14 stateful · 2026-07-13 23:33:05 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,583,940 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w49w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65b64b8a…13c7
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x8252706a…7ca5
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x2bfb71b5…3a05
0x34b655…2a6f
4 touches
1 conflict
0x4c5b064f…1498
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
10 conflicts on slot 0x65b64b8a20…3513c7
Audit this contract →
← previous block·next block →recent activity