← previous blocknext block →recent activity
Analyzing
Block #83,655,650
20 transactions · 20 stateful · 2026-06-25 18:37:36 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,655,650 · 20 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
3w05w16w212w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46d5a052…ff2e
0x34b655…2a6f
8 touches
6 conflicts
0xe6fd65c0…3a8a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xf206b7e9…4b3a
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x705f195d…cc32
0x34b655…2a6f
4 touches
1 conflict
0xcdedc01d…5e59
0x34b655…2a6f
4 touches
1 conflict
0xb1c67a7d…b9b1
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
6 conflicts on slot 0x46d5a0529d…adff2e
Audit this contract →
← previous block·next block →recent activity