← previous blocknext block →recent activity
Analyzing
Block #83,662,204
24 transactions · 21 stateful · 2026-06-25 19:21:15 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,662,204 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w09w110w211w315w416w520w021w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd63138b…63d9
0x34b655…2a6f
8 touches
6 conflicts
0x3405238a…68b6
0x34b655…2a6f
8 touches
6 conflicts
0x37a276a3…673f
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1d540370…9faf
0x34b655…2a6f
6 touches
3 conflicts
0xf4a79d55…3f4f
0x34b655…2a6f
5 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xcd63138b1f…b763d9
Audit this contract →
← previous block·next block →recent activity