← previous blocknext block →recent activity
Analyzing
Block #83,616,008
16 transactions · 16 stateful · 2026-06-25 14:12:49 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,616,008 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8a2017a…591f
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x4efb974a…6126
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x487922c6…dbd2
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0x4a1c0d58…9cff
0x34b655…2a6f
6 touches
3 conflicts
0xe155a04c…f267
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xa8a2017a7a…31591f
Audit this contract →
← previous block·next block →recent activity