← previous blocknext block →recent activity
Analyzing
Block #84,292,481
35 transactions · 26 stateful · 2026-06-28 17:22:21 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,292,481 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w09w117w018w119w220w321w422w523w628w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x0833f1ab…71e7
0x34b655…2a6f
10 touches
10 conflicts
0x23ab8481…52d5
0x34b655…2a6f
10 touches
10 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
10 touches
10 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 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