← previous blocknext block →recent activity
Analyzing
Block #88,140,000
39 transactions · 28 stateful · 2026-07-16 13:32:23 UTC
Parallelism
87/100
Blocked
57%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,140,000 · 39 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w18w29w019w020w121w222w123w224w327w128w431w233w137w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
10 touches
10 conflicts
0xc88f593e…5d93
0x336ed4…c59c
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0x47d4745e…02bb
0x336ed4…c59c
8 touches
6 conflicts
0x145b9bbf…e50e
0x34b655…2a6f
8 touches
6 conflicts
0x93c58e4d…9b32
0x336ed4…c59c
8 touches
6 conflicts
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 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity