← previous blocknext block →recent activity
Analyzing
Block #87,616,617
18 transactions · 17 stateful · 2026-07-14 03:11:37 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,616,617 · 18 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
2w04w19w010w011w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0c6e179…a103
0x34b655…2a6f
6 touches
3 conflicts
0x1041d551…7f17
0x34b655…2a6f
4 touches
1 conflict
0x1c1e591b…d93d
0x34b655…2a6f
4 touches
1 conflict
0x1c48b3ac…a03c
0x34b655…2a6f
4 touches
1 conflict
0x2a513dfb…2bb8
0x34b655…2a6f
4 touches
1 conflict
0x2c53a187…3646
0x34b655…2a6f
4 touches
1 conflict
0x46d5a052…ff2e
0x34b655…2a6f
4 touches
1 conflict
0x5debf07b…0886
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 0xa0c6e1796c…01a103
Audit this contract →
← previous block·next block →recent activity