← previous blocknext block →recent activity
Analyzing
Block #83,615,213
28 transactions · 25 stateful · 2026-06-25 14:07:29 UTC
Parallelism
86/100
Blocked
28%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,615,213 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w112w213w321w324w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x487922c6…dbd2
0x34b655…2a6f
6 touches
3 conflicts
0xaa6f28d9…83ef
0x34b655…2a6f
6 touches
3 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
6 touches
3 conflicts
0xc5df5e3a…b5f4
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity