← previous blocknext block →recent activity
Analyzing
Block #84,319,819
23 transactions · 20 stateful · 2026-06-28 20:24:27 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,319,819 · 23 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
3w06w07w114w215w116w217w218w321w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7dc64b2c…05e7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x3147083e…48d9
0x34b655…2a6f
4 touches
1 conflict
0x37005b0d…bdd0
0x34b655…2a6f
4 touches
1 conflict
0x37a86e64…3fab
0x34b655…2a6f
4 touches
1 conflict
0x3f4dc602…5a18
0x34b655…2a6f
4 touches
1 conflict
0x4bdcc5ee…7e90
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 0x7dc64b2c34…6405e7
Audit this contract →
← previous block·next block →recent activity