← previous blocknext block →recent activity
Analyzing
Block #84,335,263
14 transactions · 14 stateful · 2026-06-28 22:07:21 UTC
Parallelism
79/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,335,263 · 14 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
6w07w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xe2e45419…f17b
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
2 touches
0 conflicts
0xc08384da…ecb7
0x34b655…2a6f
2 touches
0 conflicts
0xd33e70b0…1515
0x34b655…2a6f
2 touches
0 conflicts
0xe99d8e68…a16e
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
1 conflict on slot 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity