← previous blocknext block →recent activity
Analyzing
Block #83,632,245
13 transactions · 12 stateful · 2026-06-25 16:01:21 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,632,245 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w18w110w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x369a11e2…566f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x77674e3c…0f43
0x34b655…2a6f
5 touches
3 conflicts
0x11a80388…b57d
0x40c49f…2af0
4 touches
1 conflict
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0x23ab8481…52d5
0x34b655…2a6f
4 touches
1 conflict
0xc7ead749…ace9
0x34b655…2a6f
4 touches
1 conflict
0xf0b63b44…0c3d
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 0x369a11e278…dc566f
Audit this contract →
← previous block·next block →recent activity