← previous blocknext block →recent activity
Analyzing
Block #83,637,516
27 transactions · 21 stateful · 2026-06-25 16:36:35 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,637,516 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w011w115w216w318w019w424w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd68c7c7…40b3
0x34b655…2a6f
10 touches
10 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x3af99cca…16e3
0x34b655…2a6f
6 touches
3 conflicts
0x64c171df…09d5
0xd32edf…ff58
5 touches
3 conflicts
0x1045386d…cb89
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2b1b66e9…d1c4
0x34b655…2a6f
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
10 conflicts on slot 0xbd68c7c758…bd40b3
Audit this contract →
← previous block·next block →recent activity