← previous blocknext block →recent activity
Analyzing
Block #84,023,223
18 transactions · 14 stateful · 2026-06-27 11:28:52 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,023,223 · 18 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
4w05w06w17w29w114w215w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f1
0x34b655…2a6f
6 touches
3 conflicts
0x2484cc15…5afc
0x34b655…2a6f
6 touches
3 conflicts
0x46d5a052…ff2e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x67349f95…cef6
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x9a3068dd84…9918f0
Audit this contract →
← previous block·next block →recent activity