← previous blocknext block →recent activity
Analyzing
Block #83,455,233
28 transactions · 26 stateful · 2026-06-24 20:20:16 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,455,233 · 28 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
1w05w16w210w011w112w215w216w319w420w021w124w025w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26731ffc…6b25
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x70585a8c…1b84
0x34b655…2a6f
4 touches
1 conflict
0x7a2b18bf…d24e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x26731ffcef…976b25
Audit this contract →
← previous block·next block →recent activity