← previous blocknext block →recent activity
Analyzing
Block #87,670,044
14 transactions · 13 stateful · 2026-07-14 09:08:39 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,670,044 · 14 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
1w02w13w06w17w28w29w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8f4deb0…dcf3
0x34b655…2a6f
8 touches
6 conflicts
0xdcf93b63…ae96
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x1febc2d0…0136
0x34b655…2a6f
4 touches
1 conflict
0x201ddf34…6e07
0x34b655…2a6f
4 touches
1 conflict
0x201ddf34…6e08
0x34b655…2a6f
4 touches
1 conflict
0x367e3e7f…3dd4
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
6 conflicts on slot 0xc8f4deb0cc…f2dcf3
Audit this contract →
← previous block·next block →recent activity