← previous blocknext block →recent activity
Analyzing
Block #83,631,118
24 transactions · 19 stateful · 2026-06-25 15:53:48 UTC
Parallelism
79/100
Blocked
26%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,631,118 · 24 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
1w04w19w010w111w212w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
8 touches
6 conflicts
0x5396d712…a139
0x34b655…2a6f
8 touches
6 conflicts
0x12a95d30…3af9
0x34b655…2a6f
6 touches
3 conflicts
0x2e86dd1e…dc3e
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c2
0x1b6862…e19c
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity