← previous blocknext block →recent activity
Analyzing
Block #83,583,231
16 transactions · 14 stateful · 2026-06-25 10:33:55 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,583,231 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w110w212w113w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xdb7c435f…f490
0x34b655…2a6f
7 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0x8ff8f4db…1981
0x34b655…2a6f
6 touches
3 conflicts
0xe64e6363…e676
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x5def16e6…0561
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity