← previous blocknext block →recent activity
Analyzing
Block #84,563,068
10 transactions · 9 stateful · 2026-06-29 23:26:46 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,563,068 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98d58911…19f2
0x34b655…2a6f
6 touches
3 conflicts
0xa7e45018…b59c
0x34b655…2a6f
6 touches
3 conflicts
0x25240319…98aa
0x34b655…2a6f
4 touches
1 conflict
0x255b4a3d…b0f2
0x34b655…2a6f
4 touches
1 conflict
0x33875aea…a440
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x3dcc76e9…36a6
0x34b655…2a6f
4 touches
1 conflict
0x3f75fb9e…0d2e
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 0x98d589117f…0c19f2
Audit this contract →
← previous block·next block →recent activity