← previous blocknext block →recent activity
Analyzing
Block #87,487,167
17 transactions · 15 stateful · 2026-07-13 12:45:01 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,487,167 · 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
2w03w17w28w310w413w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b580bf…f969
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x9c1e34a2…a218
0x34b655…2a6f
6 touches
3 conflicts
0xd672bfc0…1ed0
0x34b655…2a6f
6 touches
3 conflicts
0x10efb0c1…2ddc
0x34b655…2a6f
4 touches
1 conflict
0x1d73754c…2e95
0x34b655…2a6f
4 touches
1 conflict
0x2e153698…5b40
0x34b655…2a6f
4 touches
1 conflict
0x313d3d93…4aa2
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
6 conflicts on slot 0x56b580bf44…22f969
Audit this contract →
← previous block·next block →recent activity