← previous blocknext block →recent activity
Analyzing
Block #81,407,183
18 transactions · 14 stateful · 2026-06-15 08:28:00 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,407,183 · 18 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
1w02w13w04w05w18w211w212w313w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3fbc9b8…ab58
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xc5d7e85d…b578
0x40c49f…2af0
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
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 0xf3fbc9b8fe…77ab58
Audit this contract →
← previous block·next block →recent activity