← previous blocknext block →recent activity
Analyzing
Block #87,714,110
18 transactions · 14 stateful · 2026-07-14 14:03:33 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,714,110 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1ed670e…9e0b
0x34b655…2a6f
4 touches
1 conflict
0xb815046f…4859
0x34b655…2a6f
4 touches
1 conflict
0xbc4e7b49…3d2d
0x34b655…2a6f
4 touches
1 conflict
0xbf78ee7f…e7fd
0x34b655…2a6f
4 touches
1 conflict
0xc0fb0790…a482
0x34b655…2a6f
4 touches
1 conflict
0xd770071c…467d
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
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
1 conflict on slot 0xe1ed670e1b…a39e0b
Audit this contract →
← previous block·next block →recent activity