← previous blocknext block →recent activity
Analyzing
Block #87,620,318
17 transactions · 12 stateful · 2026-07-14 03:36:19 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,620,318 · 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
1w02w03w14w27w09w110w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc9fe0433…7f01
0x34b655…2a6f
8 touches
6 conflicts
0xb7b28ab0…40d1
0x34b655…2a6f
6 touches
3 conflicts
0x73ca2093…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x9cf61590…ad8c
0x34b655…2a6f
6 touches
3 conflicts
0x0837e648…cc81
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity