← previous blocknext block →recent activity
Analyzing
Block #87,624,778
26 transactions · 21 stateful · 2026-07-14 04:06:10 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,624,778 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w18w29w310w411w012w115w016w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1ee4a6d2…6389
0x34b655…2a6f
6 touches
3 conflicts
0x1f79fb1c…279e
0x34b655…2a6f
4 touches
1 conflict
0x25329a48…4e00
0x34b655…2a6f
4 touches
1 conflict
0x296e103c…993f
0x34b655…2a6f
4 touches
1 conflict
0x3225698a…9424
0x34b655…2a6f
4 touches
1 conflict
0x42341814…60f1
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