← previous blocknext block →recent activity
Analyzing
Block #83,654,637
28 transactions · 27 stateful · 2026-06-25 18:30:51 UTC
Parallelism
43/100
Blocked
59%
Avg conflicts / tx
3.43
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,654,637 · 28 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w510w611w712w813w914w1019w1225w1326w1427w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a513dfb…2bb8
0x34b655…2a6f
21 touches
55 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
20 touches
45 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0x022f72c3…07b6
0xc8689a…ee79
18 touches
36 conflicts
0x487922c6…dbd2
0x34b655…2a6f
18 touches
36 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
18 touches
36 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
18 touches
36 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
18 touches
36 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
55 conflicts on slot 0x2a513dfb89…c02bb8
Audit this contract →
← previous block·next block →recent activity