← previous blocknext block →recent activity
Analyzing
Block #83,627,983
20 transactions · 19 stateful · 2026-06-25 15:32:52 UTC
Parallelism
65/100
Blocked
37%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,627,983 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w29w010w112w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x758bd24b…cc0c
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0x124be23b…2cca
0x34b655…2a6f
6 touches
5 conflicts
0x3b8acfe4…a3d9
0x34b655…2a6f
6 touches
3 conflicts
0x5df421ff…59da
0x34b655…2a6f
6 touches
3 conflicts
0x708619a6…d52a
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
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
15 conflicts on slot 0x758bd24bd8…71cc0c
Audit this contract →
← previous block·next block →recent activity