← previous blocknext block →recent activity
Analyzing
Block #106,917,370
36 transactions · 33 stateful · 2026-09-22 02:35:10 UTC
Parallelism
78/100
Blocked
55%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,917,370 · 36 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
1w02w13w24w35w48w010w011w112w213w314w415w534w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23769ebc…c8ed
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0x81d2de5b…f95e
0x34b655…2a6f
16 touches
28 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
12 touches
15 conflicts
0xc7ce92b1…25d0
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c4
0x1b6862…e19c
10 touches
10 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
28 conflicts on slot 0x23769ebc9a…0ec8ed
Audit this contract →
← previous block·next block →recent activity