← previous blocknext block →recent activity
Analyzing
Block #87,487,172
20 transactions · 18 stateful · 2026-07-13 12:45:03 UTC
Parallelism
80/100
Blocked
28%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,487,172 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w38w09w110w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2c66a2e…150f
0x34b655…2a6f
8 touches
6 conflicts
0x82437f64…3f11
0x34b655…2a6f
8 touches
6 conflicts
0xf8c16f69…037e
0x34b655…2a6f
8 touches
6 conflicts
0xbc7c20b3…7438
0x34b655…2a6f
8 touches
6 conflicts
0x4ca81ae8…01d4
0x34b655…2a6f
6 touches
3 conflicts
0x5a2f6bbc…b925
0x34b655…2a6f
6 touches
3 conflicts
0x6eab5218…4aa1
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
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 0xe2c66a2eef…80150f
Audit this contract →
← previous block·next block →recent activity