← previous blocknext block →recent activity
Analyzing
Block #87,784,864
17 transactions · 16 stateful · 2026-07-14 21:57:01 UTC
Parallelism
59/100
Blocked
38%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,784,864 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w38w412w515w016w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f8fc992…4d3d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00893bb8…77ee
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3e644b16…807b
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 0x5f8fc9929c…884d3d
Audit this contract →
← previous block·next block →recent activity