← previous blocknext block →recent activity
Analyzing
Block #87,488,082
17 transactions · 16 stateful · 2026-07-13 12:51:07 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,488,082 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w18w09w010w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88adad52…54b7
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x418b9f6b…e8df
0x34b655…2a6f
4 touches
1 conflict
0x5fc3dad6…1b9b
0x34b655…2a6f
4 touches
1 conflict
0x636446ac…f478
0x34b655…2a6f
4 touches
1 conflict
0x636446ac…f479
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 0x88adad5202…7d54b7
Audit this contract →
← previous block·next block →recent activity