← previous blocknext block →recent activity
Analyzing
Block #105,625,642
99 transactions · 59 stateful · 2026-09-17 14:10:25 UTC
Parallelism
79/100
Blocked
63%
Avg conflicts / tx
2.12
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #105,625,642 · 99 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
1w02w13w24w06w38w09w110w211w312w414w515w616w752w857w978w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
30 touches
105 conflicts
0xaad6be10…0801
0x2a68ba…90c5
20 touches
45 conflicts
0x08cf81e6…f097
0xc8689a…ee79
12 touches
15 conflicts
0x03fccbac…059f
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xf95f86cd…e927
0x34b655…2a6f
12 touches
15 conflicts
0x9afdb944…06bd
0x37db7f…ec7b
12 touches
15 conflicts
0x76622fb2…4f08
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
105 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity