← previous blocknext block →recent activity
Analyzing
Block #83,400,014
28 transactions · 25 stateful · 2026-06-24 14:11:22 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,400,014 · 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
1w05w08w19w111w012w113w214w315w419w020w124w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x58397d66…a6bc
0x34b655…2a6f
8 touches
6 conflicts
0x379a09c4…259b
0x34b655…2a6f
8 touches
6 conflicts
0x124be23b…2cca
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb6632320…a3ce
0x34b655…2a6f
4 touches
1 conflict
0xb6b9800d…0682
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