← previous blocknext block →recent activity
Analyzing
Block #83,570,501
12 transactions · 12 stateful · 2026-06-25 09:09:07 UTC
Parallelism
42/100
Blocked
50%
Avg conflicts / tx
1.42
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,570,501 · 12 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xe64e6363…e676
0x34b655…2a6f
10 touches
10 conflicts
0x157dbfb2…4089
0x34b655…2a6f
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x63f8a50d…333b
0x34b655…2a6f
10 touches
10 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity