← previous blocknext block →recent activity
Analyzing
Block #87,707,564
18 transactions · 16 stateful · 2026-07-14 13:19:43 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,707,564 · 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
6w07w18w29w310w412w213w316w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0x13e78c51…55d1
0x34b655…2a6f
4 touches
1 conflict
0x1a625412…648b
0x34b655…2a6f
4 touches
1 conflict
0x3eeca510…5146
0x34b655…2a6f
4 touches
1 conflict
0x4f1e16d4…4833
0x34b655…2a6f
4 touches
1 conflict
0x58aa2cb3…5758
0x34b655…2a6f
4 touches
1 conflict
0x61d6f6e7…87d6
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity