← previous blocknext block →recent activity
Analyzing
Block #88,075,387
16 transactions · 15 stateful · 2026-07-16 06:20:09 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,075,387 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w07w28w39w410w012w513w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x6d22099a…6b81
0x34b655…2a6f
8 touches
6 conflicts
0x99c5409a…25b7
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x8218911e…3bed
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
10 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity