← previous blocknext block →recent activity
Analyzing
Block #87,621,355
11 transactions · 9 stateful · 2026-07-14 03:43:16 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,621,355 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b21de9f…60cd
0x34b655…2a6f
4 touches
1 conflict
0xd34b5587…cc86
0x34b655…2a6f
4 touches
1 conflict
0xd50d8366…df9c
0x34b655…2a6f
4 touches
1 conflict
0xd50d8366…df9d
0x34b655…2a6f
4 touches
1 conflict
0xa123d336…a4b2
0x34b655…2a6f
4 touches
1 conflict
0xa19591ca…ba31
0x34b655…2a6f
4 touches
1 conflict
0x47ae83ab…7e33
0x34b655…2a6f
4 touches
1 conflict
0x9d9b4da9…ecf3
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x5b21de9feb…bd60cd
Audit this contract →
← previous block·next block →recent activity