← previous blocknext block →recent activity
Analyzing
Block #84,266,620
13 transactions · 13 stateful · 2026-06-28 14:30:01 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,266,620 · 13 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
4w05w06w110w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6fd65c0…3a8a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2f3b9fca…86f4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x2c53a187…3646
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4ca3e568…4201
0x34b655…2a6f
2 touches
0 conflicts
0x7065e076…589b
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
3 conflicts on slot 0xe6fd65c0f9…793a8a
Audit this contract →
← previous block·next block →recent activity