← previous blocknext block →recent activity
Analyzing
Block #83,641,723
14 transactions · 11 stateful · 2026-06-25 17:04:40 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,641,723 · 14 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
3w09w110w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37a276a3…673f
0x34b655…2a6f
6 touches
3 conflicts
0xffb1ee54…7c2c
0x34b655…2a6f
4 touches
1 conflict
0x0782e1b1…f10a
0x34b655…2a6f
4 touches
1 conflict
0x07a0dea2…ca8c
0x34b655…2a6f
4 touches
1 conflict
0x2a9205bf…51bc
0x34b655…2a6f
4 touches
1 conflict
0x4355bbe5…0c1b
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd2862d04…388c
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 0x37a276a33f…0f673f
Audit this contract →
← previous block·next block →recent activity