← previous blocknext block →recent activity
Analyzing
Block #83,633,310
20 transactions · 16 stateful · 2026-06-25 16:08:28 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,633,310 · 20 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
7w08w111w112w213w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x785889c9…0603
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x2b2dce58…2f1d
0x34b655…2a6f
4 touches
1 conflict
0x58b4f497…6acf
0x065c9d…c394
2 touches
0 conflicts
0xf05eedb6…4dfa
0x065c9d…c394
2 touches
0 conflicts
0x6767aeb1…eabc
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity