← previous blocknext block →recent activity
Analyzing
Block #83,843,201
41 transactions · 38 stateful · 2026-06-26 15:28:59 UTC
Parallelism
59/100
Blocked
63%
Avg conflicts / tx
2.95
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,843,201 · 41 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w411w012w113w214w315w416w517w618w719w820w921w1025w528w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x38ec2c24…ef42
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x0833f1ab…71e7
0x34b655…2a6f
10 touches
10 conflicts
0xb3975d93…b4a2
0x34b655…2a6f
10 touches
10 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
10 touches
10 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
78 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity