← previous blocknext block →recent activity
Analyzing
Block #83,581,285
20 transactions · 20 stateful · 2026-06-25 10:20:58 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,581,285 · 20 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
3w04w18w09w110w211w312w413w515w218w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x157dbfb2…4089
0x34b655…2a6f
12 touches
15 conflicts
0xe64e6363…e676
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
9 touches
10 conflicts
0xd2453506…54e4
0x34b655…2a6f
6 touches
3 conflicts
0x7fe6b778…d451
0x34b655…2a6f
4 touches
1 conflict
0xb3572c95…9c4a
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity