← previous blocknext block →recent activity
Analyzing
Block #83,759,651
20 transactions · 20 stateful · 2026-06-26 06:11:23 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,759,651 · 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
1w02w13w04w09w210w311w012w114w015w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x5a30d8a9…f768
0x34b655…2a6f
4 touches
2 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x3a3097d7…2ab8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity