← previous blocknext block →recent activity
Analyzing
Block #82,974,709
48 transactions · 44 stateful · 2026-06-22 14:48:11 UTC
Parallelism
58/100
Blocked
68%
Avg conflicts / tx
3.33
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #82,974,709 · 48 txs across 20 waves · depth 20
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
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w08w29w310w411w520w621w722w823w929w1032w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
22 touches
55 conflicts
0x08913286…f0df
0x34b655…2a6f
16 touches
28 conflicts
0x6cdad76f…2bed
0x34b655…2a6f
10 touches
13 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0x56f59993…2c32
0x34b655…2a6f
10 touches
10 conflicts
0x36a49c16…89b9
0xc8689a…ee79
8 touches
6 conflicts
0x13a54fa2…5ae3
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity