← previous blocknext block →recent activity
Analyzing
Block #105,933,099
66 transactions · 49 stateful · 2026-09-18 16:00:11 UTC
Parallelism
74/100
Blocked
73%
Avg conflicts / tx
2.12
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,933,099 · 66 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w29w010w111w212w313w414w518w632w733w834w935w1036w1144w148w149w250w351w354w355w456w560w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x1b458e47…5ab5
0x34b655…2a6f
12 touches
15 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xf5b5f7…6d70
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
66 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity