← previous blocknext block →recent activity
Analyzing
Block #105,880,478
35 transactions · 35 stateful · 2026-09-18 11:34:27 UTC
Parallelism
69/100
Blocked
63%
Avg conflicts / tx
2.4
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,880,478 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w08w09w112w113w214w315w416w527w331w734w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xd17580f9…ece1
0x754704…b603
16 touches
28 conflicts
0x97e4c862…4419
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x20fcad1f…1d7d
0x34b655…2a6f
10 touches
10 conflicts
0xe569ddfe…86f9
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4ec9ff52…e6f7
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity