← previous blocknext block →recent activity
Analyzing
Block #84,333,201
10 transactions · 8 stateful · 2026-06-28 21:53:36 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,333,201 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9a9e7a5…8aec
0x34b655…2a6f
6 touches
3 conflicts
0x8a7af3fd…72a6
0x34b655…2a6f
4 touches
1 conflict
0x8a7af3fd…72a7
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x1951ee47…540f
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
3 conflicts on slot 0xf9a9e7a5e9…828aec
Audit this contract →
← previous block·next block →recent activity