← previous blocknext block →recent activity
Analyzing
Block #83,652,462
16 transactions · 14 stateful · 2026-06-25 18:16:23 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,652,462 · 16 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
2w03w14w05w16w27w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6fd65c0…3a8a
0x34b655…2a6f
14 touches
21 conflicts
0x0a4250aa…e18f
0x34b655…2a6f
10 touches
10 conflicts
0x46d5a052…ff2e
0x34b655…2a6f
8 touches
6 conflicts
0xb8217364…1764
0x34b655…2a6f
8 touches
6 conflicts
0x67bd9dc0…b04e
0x34b655…2a6f
6 touches
3 conflicts
0x6f1a10f8…5a04
0x34b655…2a6f
6 touches
3 conflicts
0x6f58168d…ea24
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
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 0xe6fd65c0f9…793a8a
Audit this contract →
← previous block·next block →recent activity