← previous blocknext block →recent activity
Analyzing
Block #83,665,099
11 transactions · 9 stateful · 2026-06-25 19:40:33 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,665,099 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00966e54…7d1d
0x34b655…2a6f
6 touches
3 conflicts
0xcc2cd268…5687
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
6 touches
3 conflicts
0x7982e638…b9c4
0x34b655…2a6f
6 touches
3 conflicts
0x1fa72d27…bccb
0x34b655…2a6f
6 touches
3 conflicts
0xf34802b3…9f11
0x1b6862…e19c
4 touches
1 conflict
0x16dce2e7…6f05
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
3 conflicts on slot 0x00966e5492…9a7d1d
Audit this contract →
← previous block·next block →recent activity