← previous blocknext block →recent activity
Analyzing
Block #87,490,161
18 transactions · 18 stateful · 2026-07-13 13:05:03 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,490,161 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w09w410w011w115w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x7cb1d883…dc23
0x34b655…2a6f
8 touches
6 conflicts
0x11ee3670…47f6
0x34b655…2a6f
4 touches
1 conflict
0x208f26b4…f48d
0x34b655…2a6f
4 touches
1 conflict
0x2c3f67c8…40c9
0x34b655…2a6f
4 touches
1 conflict
0x3d4584df…ffed
0x34b655…2a6f
4 touches
1 conflict
0x40e6ec54…fbf3
0x34b655…2a6f
4 touches
1 conflict
0x51f9769a…71a9
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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity