← previous blocknext block →recent activity
Analyzing
Block #83,630,862
22 transactions · 19 stateful · 2026-06-25 15:52:06 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,630,862 · 22 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
1w02w13w28w09w110w211w315w016w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcadc2eec…bbf5
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
6 touches
3 conflicts
0x5396d712…a139
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0x8d73b7b5…7f41
0x34b655…2a6f
4 touches
1 conflict
0xb6d45aa0…cd53
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 0xcadc2eece0…fcbbf5
Audit this contract →
← previous block·next block →recent activity