← previous blocknext block →recent activity
Analyzing
Block #88,160,445
15 transactions · 14 stateful · 2026-07-16 15:49:21 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,160,445 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w09w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddbe0a4f…f7b0
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x182c3cab…f941
0x34b655…2a6f
4 touches
1 conflict
0x1ec7ada6…505b
0x34b655…2a6f
4 touches
1 conflict
0x2afe51f4…4006
0x34b655…2a6f
4 touches
1 conflict
0x2c0a3679…8b6e
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
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
1 conflict on slot 0xddbe0a4f46…10f7b0
Audit this contract →
← previous block·next block →recent activity