← previous blocknext block →recent activity
Analyzing
Block #83,841,276
23 transactions · 21 stateful · 2026-06-26 15:16:07 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,841,276 · 23 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
4w05w16w28w09w010w311w119w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 conflicts
0xc34f7ec0…59cd
0x34b655…2a6f
6 touches
3 conflicts
0x1274880c…3cdc
0x34b655…2a6f
6 touches
3 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xf2d5b20e…9f31
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity