← previous blocknext block →recent activity
Analyzing
Block #84,093,338
19 transactions · 15 stateful · 2026-06-27 19:16:01 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,093,338 · 19 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
4w06w17w28w313w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x910be0f4…b71c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49194594…2c70
0x34b655…2a6f
6 touches
3 conflicts
0x6319ef65…5e89
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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 0x910be0f46d…1ab71c
Audit this contract →
← previous block·next block →recent activity