← previous blocknext block →recent activity
Analyzing
Block #83,642,691
19 transactions · 16 stateful · 2026-06-25 17:11:08 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,642,691 · 19 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
3w04w15w26w37w49w010w112w516w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc8dd43…8cf2
0x34b655…2a6f
12 touches
15 conflicts
0x6ca8bab1…3957
0x34b655…2a6f
10 touches
10 conflicts
0x5ed74afb…976a
0x34b655…2a6f
10 touches
10 conflicts
0x12269473…6fee
0x34b655…2a6f
8 touches
6 conflicts
0x7e6c970a…65af
0x34b655…2a6f
8 touches
6 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
8 touches
6 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 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 0x5cc8dd430f…428cf2
Audit this contract →
← previous block·next block →recent activity