← previous blocknext block →recent activity
Analyzing
Block #83,639,662
17 transactions · 17 stateful · 2026-06-25 16:50:55 UTC
Parallelism
59/100
Blocked
35%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,639,662 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x1b1df992…40eb
0x34b655…2a6f
8 touches
6 conflicts
0x049cca71…b102
0x34b655…2a6f
6 touches
3 conflicts
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x7d0b6b36…f62d
0x34b655…2a6f
4 touches
1 conflict
0x39bcab17…f79f
0x34b655…2a6f
4 touches
1 conflict
0xff4a358a…762f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
2 touches
0 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity