← previous blocknext block →recent activity
Analyzing
Block #83,656,242
18 transactions · 18 stateful · 2026-06-25 18:41:32 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,656,242 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w410w211w313w416w217w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f3fc680…f989
0x34b655…2a6f
8 touches
6 conflicts
0x705f195d…cc32
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x05b2de6d…b169
0x34b655…2a6f
6 touches
3 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd064a456…b881
0x34b655…2a6f
6 touches
3 conflicts
0xe46a9e83…22b5
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x5f3fc68024…49f989
Audit this contract →
← previous block·next block →recent activity