← previous blocknext block →recent activity
Analyzing
Block #83,627,753
24 transactions · 22 stateful · 2026-06-25 15:31:20 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,627,753 · 24 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
6w07w08w09w110w011w113w119w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x930d4cd3…d26c
0x34b655…2a6f
6 touches
3 conflicts
0x785889c9…0603
0x34b655…2a6f
6 touches
3 conflicts
0xdc54eb34…fe58
0x34b655…2a6f
6 touches
3 conflicts
0x454d8940…cfe7
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x802741e7…56b9
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7212
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity