← previous blocknext block →recent activity
Analyzing
Block #87,758,902
11 transactions · 10 stateful · 2026-07-14 19:03:17 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,758,902 · 11 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
2w03w04w16w07w28w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x378c030c…a8a5
0x34b655…2a6f
6 touches
3 conflicts
0x80bf58f2…be96
0x34b655…2a6f
6 touches
3 conflicts
0x14997ca0…3e65
0x34b655…2a6f
6 touches
3 conflicts
0xfcad4d96…c691
0x34b655…2a6f
4 touches
1 conflict
0x08cf1b01…68e9
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x59a5e379…ad8f
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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 0x378c030cda…2ba8a5
Audit this contract →
← previous block·next block →recent activity