← previous blocknext block →recent activity
Analyzing
Block #83,842,579
22 transactions · 19 stateful · 2026-06-26 15:24:49 UTC
Parallelism
82/100
Blocked
37%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,842,579 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w110w011w112w214w115w217w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f6fc26c…3e34
0x34b655…2a6f
6 touches
3 conflicts
0x8726ff39…3be8
0x34b655…2a6f
6 touches
3 conflicts
0xe2e45419…f17b
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xcd4d0c58…99c8
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 0x6f6fc26c68…133e34
Audit this contract →
← previous block·next block →recent activity