← previous blocknext block →recent activity
Analyzing
Block #83,864,347
21 transactions · 20 stateful · 2026-06-26 17:50:02 UTC
Parallelism
86/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,864,347 · 21 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
1w02w03w14w05w16w07w18w09w110w212w214w115w219w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0592331…1e7f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb173ac20…2e38
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x55f844d6…3789
0xa6afd3…d132
5 touches
3 conflicts
0xc3483764…f296
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
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 0xa059233109…d51e7f
Audit this contract →
← previous block·next block →recent activity