← previous blocknext block →recent activity
Analyzing
Block #84,059,197
67 transactions · 48 stateful · 2026-06-27 15:28:35 UTC
Parallelism
72/100
Blocked
77%
Avg conflicts / tx
3.25
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #84,059,197 · 67 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w19w210w311w412w513w614w715w816w917w1018w1119w1247w752w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
26 touches
78 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
26 touches
78 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x763dd151…d9de
0xa6afd3…d132
16 touches
28 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
14 touches
21 conflicts
0x37d5916a…e60c
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0x40c49f…2af0
14 touches
21 conflicts
0xd16df6cd…5532
0x40c49f…2af0
14 touches
21 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
78 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity