← previous blocknext block →recent activity
Analyzing
Block #83,666,296
23 transactions · 22 stateful · 2026-06-25 19:48:33 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,666,296 · 23 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
1w02w13w14w08w09w110w215w016w017w119w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc2cd268…5687
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x0c8fb32e…e2f4
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x7d4f80a4…bb17
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xcc2cd268e6…525687
Audit this contract →
← previous block·next block →recent activity