← previous blocknext block →recent activity
Analyzing
Block #83,654,567
28 transactions · 26 stateful · 2026-06-25 18:30:23 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,654,567 · 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
1w03w14w05w16w07w18w09w110w011w112w213w314w417w118w019w420w521w222w525w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x2a513dfb…2bb8
0x34b655…2a6f
10 touches
10 conflicts
0x487922c6…dbd2
0x34b655…2a6f
8 touches
6 conflicts
0x8dd1a323…8080
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x5bd818fc…4f86
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity