← previous blocknext block →recent activity
Analyzing
Block #83,641,220
23 transactions · 21 stateful · 2026-06-25 17:01:19 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,641,220 · 23 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
2w03w18w011w112w213w314w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x8f0e8a2f…a850
0x34b655…2a6f
12 touches
15 conflicts
0xf7468e81…86e5
0x34b655…2a6f
10 touches
10 conflicts
0x713529b7…9ac3
0x34b655…2a6f
8 touches
6 conflicts
0x7e6c970a…65af
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x2aba97ba…7464
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
21 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity