← previous blocknext block →recent activity
Analyzing
Block #82,967,664
30 transactions · 26 stateful · 2026-06-22 14:01:04 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #82,967,664 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w29w010w111w212w314w415w516w617w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xfcb9138a…3830
0xc8689a…ee79
6 touches
3 conflicts
0xab83f300…f8c8
0x34b655…2a6f
6 touches
3 conflicts
0xb8a785a6…c5d1
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 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 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity