← previous blocknext block →recent activity
Analyzing
Block #84,121,091
24 transactions · 21 stateful · 2026-06-27 22:20:53 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,121,091 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w08w19w210w311w412w516w117w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e346a85…e9c5
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x99910689…8959
0x34b655…2a6f
6 touches
3 conflicts
0x601978e3…1979
0x34b655…2a6f
6 touches
3 conflicts
0x8a7af3fd…72a6
0x34b655…2a6f
6 touches
3 conflicts
0x8a7af3fd…72a7
0x34b655…2a6f
6 touches
3 conflicts
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0x89096f95…8aaf
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 0x1e346a85f5…1ee9c5
Audit this contract →
← previous block·next block →recent activity