← previous blocknext block →recent activity
Analyzing
Block #106,164,538
65 transactions · 59 stateful · 2026-09-19 11:25:07 UTC
Parallelism
68/100
Blocked
83%
Avg conflicts / tx
3.2
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #106,164,538 · 65 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w36w49w520w539w845w149w351w553w654w755w858w1463w19
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0xf5b5f7…6d70
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x9430e759…86df
0x34b655…2a6f
14 touches
21 conflicts
0x73b87bc2…457a
0x34b655…2a6f
14 touches
21 conflicts
0x94dabb65…43a3
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x03d037d1…564d
0x34b655…2a6f
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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity