← previous blocknext block →recent activity
Analyzing
Block #87,735,091
18 transactions · 18 stateful · 2026-07-14 16:24:02 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,735,091 · 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
2w03w19w010w115w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f29aace…1a6c
0x34b655…2a6f
6 touches
3 conflicts
0x9243d2e7…9c5d
0x34b655…2a6f
6 touches
3 conflicts
0x22ce1aa0…6e58
0x34b655…2a6f
4 touches
1 conflict
0x285f1136…7c97
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x344bc09a…942f
0x34b655…2a6f
4 touches
1 conflict
0x3b552ea8…3a4b
0x34b655…2a6f
4 touches
1 conflict
0x4b880990…8569
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 0x8f29aace4e…351a6c
Audit this contract →
← previous block·next block →recent activity