← previous blocknext block →recent activity
Analyzing
Block #82,975,640
23 transactions · 19 stateful · 2026-06-22 14:54:25 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #82,975,640 · 23 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
1w02w13w04w15w26w37w48w59w613w614w717w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
14 touches
21 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad06
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
10 touches
10 conflicts
0x40153715…ce73
0x34b655…2a6f
10 touches
10 conflicts
0x36a49c16…89b9
0xc8689a…ee79
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x87fd591e…94fa
0x34b655…2a6f
10 touches
10 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