← previous blocknext block →recent activity
Analyzing
Block #82,335,029
57 transactions · 42 stateful · 2026-06-19 15:34:20 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
1.23
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #82,335,029 · 57 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w07w19w111w013w015w116w217w018w119w326w028w129w030w031w132w233w334w435w537w240w143w349w451w653w855w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x74c3a884…0e5f
0xd32edf…ff58
11 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
10 touches
10 conflicts
0xd1a8b9bd…6f8c
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity