← previous blocknext block →recent activity
Analyzing
Block #106,283,180
41 transactions · 39 stateful · 2026-09-19 21:22:17 UTC
Parallelism
66/100
Blocked
79%
Avg conflicts / tx
2.22
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,283,180 · 41 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w08w19w110w211w313w114w418w219w320w421w524w126w528w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x663784e7…acb8
0x34b655…2a6f
10 touches
10 conflicts
0x6412fc4f…596f
0x34b655…2a6f
8 touches
6 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xb2dbcc2d…df8a
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity