← previous blocknext block →recent activity
Analyzing
Block #83,668,983
15 transactions · 12 stateful · 2026-06-25 20:06:30 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,668,983 · 15 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
2w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c6b2fa…098d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x1f0a7466…e1b0
0x34b655…2a6f
4 touches
1 conflict
0x99ee776a…053a
0x34b655…2a6f
4 touches
1 conflict
0xa07b1442…c2c1
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
2 touches
0 conflicts
0x529110cf…1128
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x68c6b2fafb…86098d
Audit this contract →
← previous block·next block →recent activity