← previous blocknext block →recent activity
Analyzing
Block #87,252,091
11 transactions · 11 stateful · 2026-07-12 10:33:04 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,252,091 · 11 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
1w02w16w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdf06241e…adf9
0x34b655…2a6f
4 touches
1 conflict
0x57e783c1…f03d
0x34b655…2a6f
4 touches
1 conflict
0x68a07294…34ee
0x34b655…2a6f
4 touches
1 conflict
0x9aa29e0c…eb5b
0x34b655…2a6f
4 touches
1 conflict
0xa6eb8f8a…7708
0x34b655…2a6f
4 touches
1 conflict
0xb94312c7…10e3
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity