← previous blocknext block →recent activity
Analyzing
Block #82,975,092
24 transactions · 19 stateful · 2026-06-22 14:50:45 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.46
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #82,975,092 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w511w621w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0xea9e7e38…819b
0x34b655…2a6f
14 touches
21 conflicts
0x08913286…f0df
0x34b655…2a6f
12 touches
15 conflicts
0x8e507257…71c1
0x34b655…2a6f
10 touches
10 conflicts
0xe6b16f87…6af8
0x34b655…2a6f
10 touches
10 conflicts
0x36a49c16…89b9
0xc8689a…ee79
10 touches
10 conflicts
0x2eb3373a…8aff
0x34b655…2a6f
10 touches
10 conflicts
0xab3ba25f…ec78
0x34b655…2a6f
4 touches
1 conflict
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity