← previous blocknext block →recent activity
Analyzing
Block #84,535,766
19 transactions · 8 stateful · 2026-06-29 20:24:12 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,535,766 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x8cb453fd…34ab
0x34b655…2a6f
3 touches
1 conflict
0xfb0a4eb5…8be3
0x34b655…2a6f
3 touches
1 conflict
0x2328941c…84d3
0x34b655…2a6f
2 touches
0 conflicts
0x2df5ccba…a51e
0x34b655…2a6f
2 touches
0 conflicts
0x30fce83f…a1d6
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 0x793aa64d0d…fdb09d
Audit this contract →
← previous block·next block →recent activity