← previous blocknext block →recent activity
Analyzing
Block #87,524,441
22 transactions · 20 stateful · 2026-07-13 16:54:58 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,524,441 · 22 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
2w03w17w18w212w213w314w415w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdd32c46…e107
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0xe6df4062…2966
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0x943b92d0…dfee
0x34b655…2a6f
6 touches
3 conflicts
0x18cf36a6…a3a3
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
10 conflicts on slot 0xcdd32c4635…71e107
Audit this contract →
← previous block·next block →recent activity