← previous blocknext block →recent activity
Analyzing
Block #83,979,972
14 transactions · 11 stateful · 2026-06-27 06:40:42 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,979,972 · 14 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
2w05w08w110w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd01910c9…9418
0x34b655…2a6f
6 touches
3 conflicts
0xd58b9a66…1c23
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x60872583…6452
0x34b655…2a6f
6 touches
3 conflicts
0xa37d59c6…996b
0x34b655…2a6f
5 touches
3 conflicts
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x61dbf5d8…4325
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
3 conflicts on slot 0xd01910c9e4…799418
Audit this contract →
← previous block·next block →recent activity