← previous blocknext block →recent activity
Analyzing
Block #87,583,845
23 transactions · 19 stateful · 2026-07-13 23:32:27 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,583,845 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w16w28w29w310w011w413w514w120w121w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x7527802e…2ba9
0x34b655…2a6f
8 touches
6 conflicts
0x8252706a…7ca5
0x34b655…2a6f
8 touches
6 conflicts
0xa562e808…4bde
0x34b655…2a6f
8 touches
6 conflicts
0xde980d9c…7f68
0x34b655…2a6f
8 touches
6 conflicts
0x18904470…0ef9
0x34b655…2a6f
6 touches
3 conflicts
0x756ad195…36a3
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity