← previous blocknext block →recent activity
Analyzing
Block #83,671,085
18 transactions · 18 stateful · 2026-06-25 20:20:31 UTC
Parallelism
61/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,671,085 · 18 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
1w02w14w05w17w28w39w410w511w612w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c6b2fa…098d
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x65df2980…8edc
0x34b655…2a6f
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
10 touches
10 conflicts
0xbaedc843…8f5f
0x34b655…2a6f
10 touches
10 conflicts
0xd4702f73…926c
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
15 conflicts on slot 0x68c6b2fafb…86098d
Audit this contract →
← previous block·next block →recent activity