← previous blocknext block →recent activity
Analyzing
Block #87,785,530
18 transactions · 16 stateful · 2026-07-14 22:01:28 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,785,530 · 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
2w03w16w27w310w412w513w516w017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e644b16…807b
0x34b655…2a6f
10 touches
10 conflicts
0x3fde350e…8d43
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb6c52a60…0076
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2f14cd2c…b5f4
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
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 0x3e644b16f4…b0807b
Audit this contract →
← previous block·next block →recent activity