← previous blocknext block →recent activity
Analyzing
Block #83,670,244
16 transactions · 14 stateful · 2026-06-25 20:14:54 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,670,244 · 16 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
3w05w06w17w19w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206fb8db…a146
0x34b655…2a6f
10 touches
10 conflicts
0x17935a8f…a796
0x34b655…2a6f
4 touches
1 conflict
0x1951ee47…540f
0x34b655…2a6f
4 touches
1 conflict
0x1b2c54a1…5a76
0x34b655…2a6f
4 touches
1 conflict
0x37773728…f3a4
0x34b655…2a6f
4 touches
1 conflict
0x3c7c65d0…0b52
0x34b655…2a6f
4 touches
1 conflict
0x55424ff3…231a
0x34b655…2a6f
4 touches
1 conflict
0x6b47245e…a342
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 0x206fb8db95…b8a146
Audit this contract →
← previous block·next block →recent activity