← previous blocknext block →recent activity
Analyzing
Block #84,042,736
26 transactions · 24 stateful · 2026-06-27 13:38:51 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,042,736 · 26 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
1w02w13w06w09w010w112w214w215w317w121w123w024w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x793aa64d…b09c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd16df6cd…5532
0x40c49f…2af0
6 touches
3 conflicts
0x793aa64d…b09d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfb0a4eb5…8be3
0x34b655…2a6f
5 touches
3 conflicts
0x098a166d…6808
0x34b655…2a6f
5 touches
3 conflicts
0x42f6f6fd…7427
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 0x793aa64d0d…fdb09c
Audit this contract →
← previous block·next block →recent activity