← previous blocknext block →recent activity
Analyzing
Block #84,120,442
46 transactions · 39 stateful · 2026-06-27 22:16:35 UTC
Parallelism
78/100
Blocked
56%
Avg conflicts / tx
1.13
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #84,120,442 · 46 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w07w19w210w312w413w516w017w119w220w323w024w134w135w641w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xdb067026…9eb8
0x69df8a…6292
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
10 touches
10 conflicts
0x975680c7…0e39
0xa6afd3…d132
10 touches
10 conflicts
0x3287e4ec…eaa3
0xa6afd3…d132
10 touches
10 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
10 touches
10 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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity