← previous blocknext block →recent activity
Analyzing
Block #83,412,194
33 transactions · 29 stateful · 2026-06-24 15:32:44 UTC
Parallelism
79/100
Blocked
66%
Avg conflicts / tx
1.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,412,194 · 33 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
1w02w13w24w35w46w07w18w29w310w012w120w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xa9419343…28a0
0xd32edf…ff58
11 touches
15 conflicts
0xfe3bddd2…8b48
0x3bd359…433a
8 touches
6 conflicts
0xd06cc746…27e4
0x97401d…ce37
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x09a4820b…2db8
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity