← previous blocknext block →recent activity
Analyzing
Block #88,093,217
15 transactions · 14 stateful · 2026-07-16 08:19:25 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,093,217 · 15 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
1w02w13w04w15w26w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x4b0c409a…d02a
0x34b655…2a6f
6 touches
3 conflicts
0x8d989c17…e984
0x34b655…2a6f
6 touches
3 conflicts
0x9465204c…bf37
0x34b655…2a6f
6 touches
3 conflicts
0xac6f24e7…c98b
0x34b655…2a6f
6 touches
3 conflicts
0x3726966a…669d
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x4a3360a6…f6d4
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity