← previous blocknext block →recent activity
Analyzing
Block #83,665,074
17 transactions · 16 stateful · 2026-06-25 19:40:23 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,665,074 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w513w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc2cd268…5687
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0xe64e6363…e676
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x5265809c…199d
0x34b655…2a6f
8 touches
6 conflicts
0xa11d5228…4a13
0x34b655…2a6f
8 touches
6 conflicts
0x6b47245e…a342
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
15 conflicts on slot 0xcc2cd268e6…525687
Audit this contract →
← previous block·next block →recent activity