← previous blocknext block →recent activity
Analyzing
Block #83,653,065
27 transactions · 25 stateful · 2026-06-25 18:20:24 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,653,065 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w17w08w110w211w312w316w217w320w122w323w425w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x4467ecee…e95b
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc8fec9ca…2d60
0x34b655…2a6f
8 touches
6 conflicts
0x8959240e…da33
0x34b655…2a6f
6 touches
3 conflicts
0x8e739938…e7ab
0x34b655…2a6f
6 touches
3 conflicts
0xcb4784d8…e866
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity