← previous blocknext block →recent activity
Analyzing
Block #83,402,022
28 transactions · 19 stateful · 2026-06-24 14:24:47 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,402,022 · 28 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
2w05w16w27w39w410w011w412w515w116w626w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xf6476f21…3580
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xef17b8cd…9511
0x34b655…2a6f
6 touches
3 conflicts
0xf490dd39…679f
0x34b655…2a6f
6 touches
3 conflicts
0x758bd24b…cc0c
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity