← previous blocknext block →recent activity
Analyzing
Block #83,410,233
30 transactions · 23 stateful · 2026-06-24 15:19:40 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,410,233 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w010w011w112w213w316w317w019w124w425w526w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x8a1eda74…de63
0x34b655…2a6f
6 touches
3 conflicts
0x9c7571b3…9605
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 conflicts
0xc34f7ec0…59cd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x889a1747…a7ce
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity