← previous blocknext block →recent activity
Analyzing
Block #102,683,026
24 transactions · 21 stateful · 2026-09-07 06:31:25 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,683,026 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w28w010w011w112w114w115w016w218w120w321w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda09bbc9…b41b
0x34b655…2a6f
6 touches
3 conflicts
0xe53bd661…5352
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf7772b49…fc12
0x34b655…2a6f
6 touches
3 conflicts
0x4b024b98…8f37
0x34b655…2a6f
6 touches
3 conflicts
0x26c599c1…706c
0x34b655…2a6f
6 touches
3 conflicts
0x6823c28e…594c
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
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
3 conflicts on slot 0xda09bbc913…f0b41b
Audit this contract →
← previous block·next block →recent activity