← previous blocknext block →recent activity
Analyzing
Block #83,615,751
38 transactions · 33 stateful · 2026-06-25 14:11:06 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,615,751 · 38 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w27w310w011w112w213w314w415w516w631w134w435w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x487922c6…dbd2
0x34b655…2a6f
8 touches
6 conflicts
0x71632345…6ee9
0x34b655…2a6f
8 touches
6 conflicts
0x785889c9…0603
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity