← previous blocknext block →recent activity
Analyzing
Block #83,624,759
21 transactions · 20 stateful · 2026-06-25 15:11:21 UTC
Parallelism
48/100
Blocked
60%
Avg conflicts / tx
2.33
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,624,759 · 21 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w17w29w210w311w414w515w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x37a276a3…673f
0x34b655…2a6f
6 touches
3 conflicts
0x006c3b86…59a9
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
6 touches
3 conflicts
0x0835adb5…ad83
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
36 conflicts on slot 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity