← previous blocknext block →recent activity
Analyzing
Block #84,280,456
27 transactions · 19 stateful · 2026-06-28 16:02:12 UTC
Parallelism
85/100
Blocked
53%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,280,456 · 27 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
1w02w111w012w113w214w315w019w120w221w222w124w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0xb6836671…5c3c
0x34b655…2a6f
4 touches
1 conflict
0xb78ad87c…6561
0x34b655…2a6f
4 touches
1 conflict
0xe1e58d05…117f
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity