← previous blocknext block →recent activity
Analyzing
Block #83,693,442
18 transactions · 16 stateful · 2026-06-25 22:49:41 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,693,442 · 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
1w03w14w18w09w110w212w013w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2754e960…bcc1
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xe15320…7f44
4 touches
1 conflict
0xad436b12…f632
0x1111b3…4111
4 touches
1 conflict
0xcb89a818…e7c1
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0xb7fefa89…54dc
0x754704…b603
4 touches
1 conflict
0x76477ddf…b8f8
0xc8689a…ee79
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 0x2754e96062…21bcc1
Audit this contract →
← previous block·next block →recent activity