← previous blocknext block →recent activity
Analyzing
Block #87,731,426
20 transactions · 18 stateful · 2026-07-14 15:59:31 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,731,426 · 20 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
4w05w06w17w08w19w210w312w413w015w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x8df5fa2c…02e6
0x34b655…2a6f
6 touches
3 conflicts
0x3cfe4586…0bd9
0x34b655…2a6f
6 touches
3 conflicts
0x80fd3987…2314
0x34b655…2a6f
6 touches
3 conflicts
0x87d20e73…1071
0x34b655…2a6f
6 touches
3 conflicts
0xab406501…39ed
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity