← previous blocknext block →recent activity
Analyzing
Block #105,626,567
58 transactions · 46 stateful · 2026-09-17 14:15:05 UTC
Parallelism
71/100
Blocked
70%
Avg conflicts / tx
2.17
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,626,567 · 58 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
1w02w03w14w25w37w08w09w110w211w012w313w423w124w226w327w428w529w530w151w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x62910921…3016
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x8f84702c…c5f9
0x34b655…2a6f
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity