← previous blocknext block →recent activity
Analyzing
Block #87,668,331
13 transactions · 11 stateful · 2026-07-14 08:57:13 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,668,331 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w28w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588c5b6a…60d2
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xcffc17bc…3544
0x34b655…2a6f
4 touches
1 conflict
0x13ed417e…a863
0x34b655…2a6f
4 touches
1 conflict
0x842389d2…e6ea
0x34b655…2a6f
4 touches
1 conflict
0x8f1b3f9a…d537
0x34b655…2a6f
4 touches
1 conflict
0x958969ed…efda
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
3 conflicts on slot 0x588c5b6adb…3060d2
Audit this contract →
← previous block·next block →recent activity