← previous blocknext block →recent activity
Analyzing
Block #84,253,523
17 transactions · 14 stateful · 2026-06-28 13:02:46 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,253,523 · 17 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
6w07w18w09w112w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe27b0bdf…b21a
0x34b655…2a6f
8 touches
6 conflicts
0xb6c88e49…7bbf
0x34b655…2a6f
6 touches
3 conflicts
0xc47ca59a…b171
0x34b655…2a6f
6 touches
3 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0x38ec2c24…ef42
0x34b655…2a6f
6 touches
3 conflicts
0x3f7d6538…1779
0x34b655…2a6f
4 touches
1 conflict
0x423af0c6…8145
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xe27b0bdf93…61b21a
Audit this contract →
← previous block·next block →recent activity