← previous blocknext block →recent activity
Analyzing
Block #83,876,421
20 transactions · 19 stateful · 2026-06-26 19:10:36 UTC
Parallelism
70/100
Blocked
68%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,876,421 · 20 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
1w02w03w15w16w07w18w29w310w411w512w113w214w217w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x785889c9…0603
0x34b655…2a6f
6 touches
3 conflicts
0xc5ee2a98…54a8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x760ee5b9…edb6
0x34b655…2a6f
4 touches
1 conflict
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0x90a9e3f8…17ab
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity