← previous blocknext block →recent activity
Analyzing
Block #83,616,023
19 transactions · 19 stateful · 2026-06-25 14:12:55 UTC
Parallelism
63/100
Blocked
32%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,616,023 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w513w017w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe155a04c…f267
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x487922c6…dbd2
0x34b655…2a6f
10 touches
10 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
10 touches
10 conflicts
0x01179535…e4e8
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x3e875d66…bc88
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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
15 conflicts on slot 0xe155a04cc1…f3f267
Audit this contract →
← previous block·next block →recent activity