← previous blocknext block →recent activity
Analyzing
Block #84,190,520
18 transactions · 15 stateful · 2026-06-28 06:02:52 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,190,520 · 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
4w05w06w17w08w110w112w214w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x510718d9…a026
0x34b655…2a6f
6 touches
3 conflicts
0x5d7f309d…5145
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x99c320a0…b4a8
0x34b655…2a6f
6 touches
3 conflicts
0xb577a4a7…a670
0x34b655…2a6f
6 touches
3 conflicts
0x18b11fba…c92a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
6 touches
3 conflicts
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 0x510718d992…96a026
Audit this contract →
← previous block·next block →recent activity