← previous blocknext block →recent activity
Analyzing
Block #83,616,744
30 transactions · 27 stateful · 2026-06-25 14:17:44 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,616,744 · 30 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
1w02w14w09w010w112w113w016w217w124w225w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x785889c9…0603
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0x48aded11…c45c
0x34b655…2a6f
4 touches
1 conflict
0x6290cbed…b15f
0x34b655…2a6f
4 touches
1 conflict
0x6dbd606f…b4dd
0x34b655…2a6f
4 touches
1 conflict
0x80269196…b9e2
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 0x785889c9fb…160603
Audit this contract →
← previous block·next block →recent activity