← previous blocknext block →recent activity
Analyzing
Block #83,036,383
13 transactions · 10 stateful · 2026-06-22 21:41:02 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,036,383 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x744e0a36…70f7
0x34b655…2a6f
4 touches
1 conflict
0x30c22c15…efc5
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x086db8fc…0024
0x34b655…2a6f
2 touches
0 conflicts
0x08913286…f0df
0x34b655…2a6f
2 touches
0 conflicts
0x112ff1ac…7a3f
0x34b655…2a6f
2 touches
0 conflicts
0x20079932…08b5
0x34b655…2a6f
2 touches
0 conflicts
0x309eb1ab…f5c8
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x744e0a3655…6d70f7
Audit this contract →
← previous block·next block →recent activity