← previous blocknext block →recent activity
Analyzing
Block #83,467,335
21 transactions · 15 stateful · 2026-06-24 21:41:07 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,467,335 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w210w011w112w213w315w016w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9610cea3…6614
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
6 touches
3 conflicts
0x29633a56…3007
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
4 touches
1 conflict
0xdb067026…9eb8
0x69df8a…6292
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 0x9610cea36c…a96614
Audit this contract →
← previous block·next block →recent activity