← previous blocknext block →recent activity
Analyzing
Block #83,669,796
15 transactions · 14 stateful · 2026-06-25 20:11:54 UTC
Parallelism
53/100
Blocked
43%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,669,796 · 15 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
3w04w15w26w37w48w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x913ebf0e…d816
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x65df2980…8edc
0x34b655…2a6f
8 touches
6 conflicts
0xd4702f73…926c
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0x68c6b2fa…098d
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
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
21 conflicts on slot 0x913ebf0e0a…d2d816
Audit this contract →
← previous block·next block →recent activity